Anton (pendalf2008),
I think your strategy of trying to deflect guilt onto someone else (who has tracked you) is not a good strategy for you. I've given you plenty of chances to do the right thing but if you want to make the situation worse for yourself, then by all means.
For those reading this: Essentially what happened here was an exchange was robbed of a high number of BTC. I was hired by the exchange to do post-hack forensic work and track down the attacker. Unfortunately for our Ukrainian friend pendalf2008 he left his IP address in Apache's logs when he initially discovered the attack vector. Once he realized he had found the attack vector, and also realized he was connected via his home IP he then went ahead and jumped onto a VPN/Proxy/VPS from Germany to finish the steal.
For respect of the Exchange, I left attack vector, exchange url and other requests out of the logs.
109.108.237.17 - - [11/Mar/2014:03:47:00 +0100] "GET /favicon.ico HTTP/1.1" 304 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:48:11 +0100] "GET [attack vector] HTTP/1.1" 200 23 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:48:20 +0100] "GET [attack vector] HTTP/1.1" 200 169 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:48:33 +0100] "GET [attack vector] HTTP/1.1" 200 41 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:48:43 +0100] "GET [attack vector] HTTP/1.1" 200 708 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:48:59 +0100] "GET [attack vector] HTTP/1.1" 200 201 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:51:28 +0100] "GET / HTTP/1.1" 200 59770 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:51:40 +0100] "GET [attack vector] HTTP/1.1" 200 57467 "
https://www.[exchange]/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:51:42 +0100] "GET [attack vector] HTTP/1.1" 200 367738 "
https://www.[exchange]/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:52:28 +0100] "GET [attack vector] HTTP/1.1" 200 59770 "
https://www.[exchange]/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:52:58 +0100] "GET [attack vector] HTTP/1.1" 200 60053 "
https://www.[exchange]/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
109.108.237.17 - - [11/Mar/2014:03:53:19 +0100] "GET [attack vector] HTTP/1.1" 200 294 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
After he discovered the attack vector he waited some time and came back from his new connection:
78.47.55.70 - - [11/Mar/2014:06:22:19 +0100] "GET [attack vector] HTTP/1.1" 206 28532736 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
78.47.55.70 - - [11/Mar/2014:06:23:27 +0100] "GET [attack vector] HTTP/1.1" 304 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
78.47.55.70 - - [11/Mar/2014:06:28:00 +0100] "GET [attack vector] HTTP/1.1" 304 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36"
Notice the same exact UserAgent? Hitting the same attack vector as no one else did in the logs.
Once he got the access to what he needed, he transferred funds out to two wallets which I can not name as of yet. After BTC was stolen, he connected back to his exchange account to check his balances from: 109.108.238.71 with an Opera User-Agent. The same IP also listed as accessing his 'pendalf2008' user account on the exchange. In total he has connected to his same account using 3 IP addresses: 109.108.238.71, 109.108.238.161 and 109.108.237.17 all hosted by Everest ISP in Ukraine, Vinnitsa.
Once we confirmed it was his IP that attacked the server initially, and confirmed all three IP addresses from the same ISP to the same town in UA logged into the 'pendalf2008' account we then began finding personal information on who he was. We doxed him. Contacted him. And instead of admitting the fault, and simply returning BTC he has resulted to deflecting the situation.
Like I said in prior messages Anton, I'm a security researcher tracking a Bitcoin thief. Apparently you are that thief. Now unless you allow someone to use your IP addresses to get on to the Internet then everything points to you. If you know who stole the BTC then contact me privately and we can easily resolve the issue. If you do not comply, then all of this information with full unredacted logs will be sent to the authorities and they will have to handle you.
So tell me what you want to do.
If you don't want to deal with me, fine so be it. Contact the exchange you robbed and return their BTC.
Good day.