Hey /gee/, I’m looking for solid resources on malware development, particularly books that aren’t outdated. I’m not interested in basic "hacking" guides, but something that dives deeper into how modern malware is created and operates. Any recommendations?
Wholesome frog and swede image or something
windows internals + maldevacademy
>>102423935It's a dark art. You're not gonna find anything, only RE guides. Just learn low-level languages like C, ASM, C++ or Rust even. Good luck
>>102423935wholesome
>>102423935It really, really depends on your end goal. Are you looking to develop malware for Windows specifically, or for other operating systems like Linux? If you're interested in creating something like ransomware, which could encrypt files and demand a ransom for decryption, you’ll need to explore various techniques for encryption and secure communications. For a practical start, I’d suggest looking into Windows internals to understand the operating system’s behavior and vulnerabilities. Also, consider learning Rust. It’s a language that’s increasingly used in security and malware development due to its focus on safety and performance. Rust is challenging to reverse engineer because of its strong type system and memory safety features, which can make it harder to analyze and decompile compared to languages with less strict safety guarantees.
>>102424039edit: I know Linux is technically a kernel, but I mean the entire OS ecosystem built around it
>>102423965this
>>102423935>I’m not interested in basic "hacking" guides, but something that dives deeper into how modern malware is created and operatesHave you even read the "basic" hacking guides? Because they do cover how shit operates (unless it's just a Kali-Linux tutorial).>outdatedIf someone publishes an exploit, then no shit it gets patched shortly thereafter. But you said you wanted to learn how stuff operates, and the principles of network communication, command and control, attack payloads, encryption, etc... are still there.Maybe there's some new stuff like I2P or TOR, or interesting fingerprinting techniques particular to modern environments (e.g. Docker/WSL)? But how about you actually fucking read a book first, rather than navel-gazing about the speculative value of books because they were published 10 years ago. It's a fucking book, they don't take that long to read. Then decide its value.
