Whether in movies or mainstream media, hackers are often romanticized: they are painted as black magic wizards, nasty criminals, or, in the worst cases, as thieves with a hood and a crowbar.

In reality, the spectrum of the profile of the attackers is extremely large, from the bored teenager exploring the internet to sovereign State's armies as well as the unhappy former employee.

What are the motivations of the attackers? How can they break seemingly so easily into any network? What do they do to their victims?

We will put on our black hat and explore the world of offensive security, whether it be cyber attacks, cybercrimes, or cyberwar.

Scanners, exploits, phishing toolkit, implants... From theory to practice, we will explore the arcane of offensive security and build our own offensive tools with the Rust programming language, Stack Overflow's most loved language for five years in a row.

Which programming language allows to craft shellcodes, build servers, create phishing pages? Before Rust, none! Rust is the long-awaited one-size-fits-all programming language meeting all those requirements thanks to its unparalleled guarantees and feature set. Here is why.

DRM Free, of course :)

Who this book is for

This is NOT a 1000th tutorial about sqlmap and Metasploit, nor will it teach you the fundamentals of programming.

Instead, it's a from-theory-to-practice guide and you may enjoy it if any of the following:

• You keep screaming "show me the code!" when reading about cyber attacks and malwares
• You are a developer and want to learn security
• You are a security engineer and want to learn Rust programming
• You want to learn real-world and idiomatic rust practices
• You believe that the best defense is thinking like an attacker
• You learn by building and love to look under the hood
• You value simplicity and pragmatism
• You develop your own tools and exploits with Python, Ruby, C, Java...
• You want to learn real-world offensive security, not just pentesting
• You want to start making money with bug bounty programs
• You prefer getting things done over analysis paralysis

But I repeat, this book is NOT a computer science book.