klee's hacked 1170 btc, Part II

[SirChiko]

How can we merge the two threads?

maybe lock one of them with a link post to the active thread in the locked one?
Im not sure that is what you want...

Probably the best soulution, just make sure that your post is last and it forwards to another thread.

[hollowframe]

The fear of being caught is definitely there for the thief. A HUGE amount of btc was stolen, so morals are out the window. The 462 btc being returned is not out of good faith but rather the fear being caught. Otherwise, one of the condition wouldn't have been to lock the original thread. He probably already knows of the evidence that has been left behind.

I doubt the hacker knew just how much he was going to be able to get away with when he got the credentials to klees wallet, I think he really just got lucky and is probably not very good a "covering his tracks"

I think that the hacker really doesn't know how much evidence was left behind and decided to return part of the coins to be a little more certain that he would not be caught.

[seandaniel]

1170 BTC is very very huge amount..

[Benjig]

The fear of being caught is definitely there for the thief. A HUGE amount of btc was stolen, so morals are out the window. The 462 btc being returned is not out of good faith but rather the fear being caught. Otherwise, one of the condition wouldn't have been to lock the original thread. He probably already knows of the evidence that has been left behind.

I doubt the hacker knew just how much he was going to be able to get away with when he got the credentials to klees wallet, I think he really just got lucky and is probably not very good a "covering his tracks"

I think that the hacker really doesn't know how much evidence was left behind and decided to return part of the coins to be a little more certain that he would not be caught.

The hacker is a noob one and probably stupid, he just got lucky, the groups of hackers who hack exchanges dont "negotiate".

So we have an advantage here

[Marbit]

How can we merge the two threads?

PM a mod to do it. I'm a mod on an SMF forum and I have this ability, so they likely do as well. I would PM malevolent or one of the global mods. Seems better than locking one.

[zvs]

The fear of being caught is definitely there for the thief. A HUGE amount of btc was stolen, so morals are out the window. The 462 btc being returned is not out of good faith but rather the fear being caught. Otherwise, one of the condition wouldn't have been to lock the original thread. He probably already knows of the evidence that has been left behind.

I doubt the hacker knew just how much he was going to be able to get away with when he got the credentials to klees wallet, I think he really just got lucky and is probably not very good a "covering his tracks"

I think that the hacker really doesn't know how much evidence was left behind and decided to return part of the coins to be a little more certain that he would not be caught.

The hacker is a noob one and probably stupid, he just got lucky, the groups of hackers who hack exchanges dont "negotiate".

So we have an advantage here

Probably a dropbox employee, lol.

Why would he give anything back?  Unless he was giving the whole amount back minus the bounty, which would actually make some sense..  re; you offered this reward, i am giving it all back now minus the reward, be more careful in the future, best of luck, thanks for all the chips

[Marbit]

I'm hearing a lot about Dropbox associated with compromised data. Is there any central place where this is being discussed? Is there anything credible that points to employees compromising accounts?

[Benjig]

Probably a dropbox employee, lol.

Why would he give anything back?  Unless he was giving the whole amount back minus the bounty, which would actually make some sense..  re; you offered this reward, i am giving it all back now minus the reward, be more careful in the future, best of luck, thanks for all the chips

Dropbox had nothing to do with it.  There were multiple thieves involved but Klee knows one of the thieves personally.  She is a small, thin woman with dark hair in her thirties.

So why dont he make his moves outside and get this woman as fast as possible so people here can stop making maps on the blockchain.

[hollowframe]

The fear of being caught is definitely there for the thief. A HUGE amount of btc was stolen, so morals are out the window. The 462 btc being returned is not out of good faith but rather the fear being caught. Otherwise, one of the condition wouldn't have been to lock the original thread. He probably already knows of the evidence that has been left behind.

I doubt the hacker knew just how much he was going to be able to get away with when he got the credentials to klees wallet, I think he really just got lucky and is probably not very good a "covering his tracks"

I think that the hacker really doesn't know how much evidence was left behind and decided to return part of the coins to be a little more certain that he would not be caught.

The hacker is a noob one and probably stupid, he just got lucky, the groups of hackers who hack exchanges dont "negotiate".

So we have an advantage here

Well there is potentially an upside to negotiating as even if you cannot trace the bitcoin from point A to point B, it would still be possible to watch for large transactions from known bitmixer addresses that happened after the hack took place to try to determine where the hacker's mixed bitcoin are. This is much more advanced that what is available on blockchain.info and would only be possible with large amounts.

Since the max delay that can be used with bitmixer is 12 hours and we know the ~time the coins were sent to bitmixer we could look at all the output addresses from known bitmixer addresses and look for combinations of outputs that equal to the amount of the stolen coins +-5%. I don't know how much business that bitmixer does per day, but I doubt that it is thousands of bitcoin per day.

[klee]

Probably a dropbox employee, lol.

Why would he give anything back?  Unless he was giving the whole amount back minus the bounty, which would actually make some sense..  re; you offered this reward, i am giving it all back now minus the reward, be more careful in the future, best of luck, thanks for all the chips

Dropbox had nothing to do with it.  There were multiple thieves involved but Klee knows one of the thieves personally.  She is a small, thin woman with dark hair in her thirties.

So why dont he make his moves outside and get this woman as fast as possible so people here can stop making maps on the blockchain.

He is a troll ignore him..

[klee]

You have been reported troll 

[whitefly]

Sad to see that amount stolen, I feel sorry for klee.

[Somekindabitcoin]

I need that bounty, so I will help search for this ish.

[rapport]

Hacker definitely scared; asking for thread to be closed.  Go get him.

[Somekindabitcoin]

You have been reported troll 

Can't you see the IP address of the person who accessed your Dropbox? If not, you could probably email support asking that question too.

[klee]

@haploid23 lock this thread please, I will open a new self moderated one!

[haploid23]

As per klee's request in PM and in here, I've locked the thread. We don't need 2 concurrent ones running anyways since he has unlocked the other one.