Download the book and the labs
Download the textbook (PDF)Free. 20 chapters, 49 labs, 316 pages.
Download the lab programs (zip)Password: dboudreau.dev. Every lab program compiled, plus the dataset for Lab 12.5. The password only keeps scanners from opening the file in transit.
Warning
In your VM environment only. They are harmless training samples, but they act like the malware they imitate and antivirus will flag them.
Anyone can do this with little to no knowledge. If you can build a LEGO kit, disassemble it and rebuild it, you can do this too. Reverse engineering is the same job on software: take a finished thing apart, work out what each piece does, and write down how it fits together.
Prefer to read it here? Open the textbook in your browser.
1. Why it is worth learning
Reverse engineering is how you find out what a program does when nobody will tell you. Malware analysts use it on samples. Vulnerability researchers use it to find the bug before somebody else does. Defenders use what they find to write YARA and Sigma rules that catch next week’s build, not only yesterday’s file. It also recovers lost source, gets two systems talking when nobody documented the protocol, and checks what a vendor really ships.
2. What is in the book
Twenty chapters and 49 labs, from your first hex byte to detections built from what you find. Chapters 5 to 7 take the same password check through IDA Free, Ghidra and dnSpy, so you can compare the three tools on one problem. After that it covers dynamic analysis, config extraction, YARA and Sigma, entropy and packers, cryptography, threat intelligence, protectors, and where AI helps and where it lies to you. Most labs start from a harmless program you compile yourself. Every instrument in the Lab on this site has a matching lab in the book.
3. The labs and the source
The archive holds the compiled programs. The sources, a build script and checksums are on GitHub in Reverse Engineering Textbook Labs, so you can read what you are about to run. A kill switch, a domain generator, a renamed system tool and a packed binary all live in there, so use a VM you can revert. If your antivirus eats half the folder, you are in the right place.
4. Do it live
Compile it, run it, break it, run it again. That is the whole method.