Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Mega-TuT] A Beginners Guide To Keylogging PART 2
Part 1:

[Image: differencebetween1.png]
[Image: differencebetween2.png]

There is one major defining difference between a stealer and a keylogger. A stealers purposes is to steal passwords that have been saved in the browser/application. Ever logged into something and your browser prompted you to save the password? This is what stealers steal. They are good for massivley grabbing passwords and quickly. Once run they do not continue to steal until run again.

[Image: whatisnet.png]

.Net Framework is a very in-depth concept from Microsoft. While you don't need to know (or should you really care) you should know that most keyloggers are written in Visual Basic .Net, giving it a dependancies. Depending on who made it (whether they suck or not) you may have to install a specific version (.Net 4.0). Most computers (99%) come with .Net 2.0 installed. Your output will also requrie a specific framework (depending on which one you use).

[Image: whataregoodloggers.png]

This is like asking what your favorite ice cream flavor is! There is no "correct" answer. It's best to go and figure things out for yourself. Being spoon fed information doesn't help you grow intellectually.

[Image: upsidetokeyloggers.png]

Keyloggers are great for having massive amounts of slaves. They will constantly send you their info and passwords without you having to do anything. They are more stable that other types of malware and are easier to write. They are also extremeley beginner friendly, and that is why they are so popular.
[Image: downsidetokeyloggers.png]

There's one major downside to keyloggers. Well two, but the second is a downside for all types of malware. The first is that (most) keyloggers don't allow you to have any control once you've infected your slave. You have no control, you can't stop logs, you can't do anything really. Keyloggers are starting to add in remote logging and this is slowly growing to be more and more advanced. The second downside is the .Net dependancy for most keyloggers. This is actually a downside for a lot of malware.

[Image: iwanttomakemyown.png]

Well, aren't you ambitious!? It's great that you want to learn, but please...[color=#1e90ff]please do not copy and paste public source! Actually learn it for yourself! Once you've done that and made one, don't release it unless it's actually advanced/totally yours. There are plenty of ones on the market. Anyway, to learn how to make a keylogger, you'll need to figure out what language. For beginners I recommend Visual Basic .Net. Learn about SMTP mailing, and keyboard hooks. Then learn about filesplitting. There are plenty of guides on this forum, just search around!

[Image: ivebeeninfected1.png]
[Image: whatdoido.png]

Firstly, you are in the wrong place. You'll want to do numerous scans with several different scanners (MBAM, ESET, Your Antivirus). I'd also recommend looking into getting Keyscrambler which can be found on Google. Be cautious when downloading things and be sure to keep backups!

[Image: conclusionv.png]

Well, this tutorial was a lot longer than I anticipated, it spans from two posts and covers everything you could possibly need to know about keylogging. Hopefully this will help some people out and will reduce the amount of pointless threads in this section. If this tutorial helped you, post what you thought of it!

убийство. #RIP Unsolidarity

Donations: 1Ebwae9KypteHuaZUe8rW9DpzAPY9rBKFV

Forum Jump:

Users browsing this thread: 1 Guest(s)