A couple of questions about key logging

[r4kk00n]

I have been doing research on key loggers, and am confused/curious about some things:

Most of the sites I have been reading say that the best way to have a FUD keylogger is to code your own and encrypt it using a crypter you code yourself as well.  They say that it is best to code the logger and the crypter in c and/or assembly .

A couple of sites said that coding the keylogger in python then compiling into an exe will throw off a lot of AVs....

I don't have much background in this kind of stuff, so I am confused about the seeming contradiction in information.
Is python a viable choice for key loggers and/or crypters?

[gh05t3d]

In my opinion what matters the most is a good crypter. If the keylogger has the "melt" option it will install and won't be detected that easy. But you need a good crypter for it,and be careful. Almost all crypters posted for free in forums are backdoored (infected).

[proxx]

In my opinion what matters the most is a good crypter. If the keylogger has the "melt" option it will install and won't be detected that easy. But you need a good crypter for it,and be careful. Almost all crypters posted for free in forums are backdoored (infected).

Read again , OP talks about doing it himself, not using some green glowing skidthingy.


@OP

Python would work just like any other language , the downside to it is that it would be easy to peel down  or hard to hide, windows doesnt ship with an interpreter so you would need something like py2exe to make it portable, this is not as pretty as it sounds.

Also a C or assembly program would be much smaller , if you only expose the binary it will be harder to reverse engineer.
Problem is not so much in the logging part its about moving the data in a way that can go undetected, the traditional FTP methods are likely to set off all sorta windows toys.

Anyway there should be plenty of examples , looking at your post it is pretty clear you will have to learn how to code.
Start with something easier and think of the problem in the meanwhile.

You could template it in python , make sure you understand the networking and the OS part of the story, then move up to another language, there are plenty choices.

[Deque]

I have been doing research on key loggers, and am confused/curious about some things:

Most of the sites I have been reading say that the best way to have a FUD keylogger is to code your own and encrypt it using a crypter you code yourself as well.  They say that it is best to code the logger and the crypter in c and/or assembly .

A couple of sites said that coding the keylogger in python then compiling into an exe will throw off a lot of AVs....

I don't have much background in this kind of stuff, so I am confused about the seeming contradiction in information.
Is python a viable choice for key loggers and/or crypters?

There is the common misconception that programming the harder way (more low-level) is always better. Although it will serve to impress more people if you program everything in assembly, it is not necessarily the best option.

Especially if you are just starting out, you might just try what you can do with "easy" languages like Python and where the boundaries are. Learn it by doing it. You will discover it yourself. Assembly or C give you more control, but need more time and you will likely produce more bugs with them.

If you are not experienced, don't overthink the language for your project. Just do it. You need to learn, the project may likely fail, but that is normal. The learning should be your goal.

coding the keylogger in python then compiling into an exe will throw off a lot of AVs....

It will indeed, because not every AV is able to unpack the wrapped file. It is not always a matter of how hard it is to reverse engineer. These files are very easy to analyse, but if the technology for unpacking a particular wrapper is not there, the file cannot get a proper detection and might just be blacklisted.