Live data from Hacker News

How I Cracked a Keylogger and Ended Up in Someone's Inbox

trustwave.com

31–40 of 108 posts

Re: How I Cracked a Keylogger and Ended Up in Someone's Inbox

#31
post #16

Website that we were running was under DDOS couple of years ago, what we did is we took ips of servers that made ddos. Then we scanned the ports, found vulnerability in the application that was running on it then get into the server using this vulnerability. We checked open connections and found one used for command and control server (irc server) then we listened to irc channel. DDOSers were talking private things o…

> found vulnerability in the application that was running on it

Could you give more a more detailed explanation on how you did that?

Re: How I Cracked a Keylogger and Ended Up in Someone's Inbox

#33

Earlier quoted context omitted.

Keyloggers simply record all key presses so if you delete the credentials for a game and someone then tries to run that game the first thing you catch is the credentials to log in again. The most obvious way is to hook the message stream from the window manager to the applications, windows provides some convenient hooks for this.

as for the first point, yup, I understood that from the article; I probably should have used "similar to Steam" rather than "like Steam". I mostly meant, you'd get a long stream of characters and you'd have to manually try to dejumble them. Whereas, I believe if you go by your second point, you can see "Ok, the user put username in the username textfield, password in the password field, address in the address textfie…

Most of them usually show specifics, the keylog file is often less of a jumble and more of like:

{TAB}{TAB}{CURRENT WINDOW: Steam - Log in}{TAB}username{LEFTCLICK}password{LEFTCLICK}{CURRENT WINDOW CHANGED: Steam: Home}

Re: How I Cracked a Keylogger and Ended Up in Someone's Inbox

#34
post #7

That's a great little story, interesting to read how these sorts of scams are carried out, but I also found the code analysis and decompilation tale fun!

I agree, it's amazing how stupid criminals can be, even online. It's scary to think what someone as smart as these security researchers could do if they went black hat...

I don't think criminals are stupid; they're simply lazy. They put the minimum amount of effort is into a scam like this in order to make it profitable.

An off the shelf key logger is used; a couple of stolen email accounts, and a spammer is used for delivery. There are automated tools that will pack the key logger executable in a word document also.

As for the part of the security researcher; reversing .net code isn't challenging. This is by design - the framework does not obfuscate or make it challenging to look at the code. The author of the key logger could have built in protections or obfuscated his executable but for one reason or another has not.

Most likely all of the reversing or analysis was also done with automated tools, and the analyst simply had to run them. OfficeMalScanner can be used to locate packed executables in MS documents and extract them, and then it is simply a matter of dumping the binary in the .NET decompiler of your choice (the author uses ILSpy, I personally prefer RedGate Reflector) and looking at the code.

IMO this is a marketing piece that happens to have an interesting story attached to it.

Re: How I Cracked a Keylogger and Ended Up in Someone's Inbox

#35
post #28
post #16

Website that we were running was under DDOS couple of years ago, what we did is we took ips of servers that made ddos. Then we scanned the ports, found vulnerability in the application that was running on it then get into the server using this vulnerability. We checked open connections and found one used for command and control server (irc server) then we listened to irc channel. DDOSers were talking private things o…

I’ve had a very similar experience – I’m surprised I’m not the only one who did that. I’d have expected the DDoSers to have better security

Pretty much everyone is very bad at security

Re: How I Cracked a Keylogger and Ended Up in Someone's Inbox

#37
post #6
post #5

Scary that a vulnerability that old is still worth exploiting.

In spam runs a success factor of one in thousand still can pay off. I'm afraid their results are better as that.

It doesn't have to be the case that it actually paid off. All we know is the spammer thought it would.

Re: How I Cracked a Keylogger and Ended Up in Someone's Inbox

#38
post #16

Website that we were running was under DDOS couple of years ago, what we did is we took ips of servers that made ddos. Then we scanned the ports, found vulnerability in the application that was running on it then get into the server using this vulnerability. We checked open connections and found one used for command and control server (irc server) then we listened to irc channel. DDOSers were talking private things o…

These days I'd be worried about CFAA or otherwise getting V& for this. In the "good old days", it was possible to get away with and laugh about this type of vigilante justice. These days though, you're more likely to wind up in prison. No longer worth it for lulz. Sad times now, but good memories.

Re: How I Cracked a Keylogger and Ended Up in Someone's Inbox

#39
post #28
post #16

Website that we were running was under DDOS couple of years ago, what we did is we took ips of servers that made ddos. Then we scanned the ports, found vulnerability in the application that was running on it then get into the server using this vulnerability. We checked open connections and found one used for command and control server (irc server) then we listened to irc channel. DDOSers were talking private things o…

I’ve had a very similar experience – I’m surprised I’m not the only one who did that. I’d have expected the DDoSers to have better security

Why? DDOSers are mostly dumb skids who rent botnets.
Post reply on HN