6 replies to this topic

[seven]

I am enjoying it currently, I figure why not share it with everyone else
http://0x4f4c.awards...es/Backdoor.pdf

Have a good one!

[thenotwist]

Damn that's a sweet paper! Thx for the link.

[Aghaster]

Except for the multiple spelling mistakes, horribly indented code, and some weird coding style, and a "1337 title", it does contain some interesting information. I've just compiled the keylogger example because it is using a different method than the one I'm currently using in the keylogger I'm working on. In fact, this guide described the GetAsyncKeyState in a loop method as being the easiest but the least efficient (and that was the method I'm using). Right, the hooking method seems better, so I'll integrate this in my code with some modifications. Good find.

[seven]

Despite that, ( I can still read it but I do agree with the spelling errors and sloppy code ) it has helped me to further understand backdoors. I hope it helps more people out.

[Tonto]

That keylogger is just a poor corruption of this

http://web.archive.o...hp?newsid=10952

>> some weird coding style

It's patchwork. Copy + pastes from all over the web.

Nomenumbra is just an egowhore, plagiarizes, but definitely writes some good stuff anyways

[prick]

Right, the hooking method seems better, so I'll integrate this in my code with some modifications. Good find.

Apart from the almost guaranteed detection you'll automatically get from the majority of AV's

[thenotwist]

Right, the hooking method seems better, so I'll integrate this in my code with some modifications. Good find.

Apart from the almost guaranteed detection you'll automatically get from the majority of AV's

i used a hook in my keylogger and it's not being detected by antivir, norton, nod32 and kaspersky