Reverse Engineering
| Field | Value |
|---|---|
| Module ID | 406 |
| Difficulty | Hard |
| Tier | Tier I |
| Category | Defensive |
| Estimated Time | 2 hours |
| Cubes Earned | 10 |
| Experience Points | 800 |
| Creators | letsdefendio |
| Last Updated | 2026-06-24T18:43:24.000000Z |
| URL | https://academy.hackthebox.com/app/module/406 |
Module Includes
- 8 Sections
- 1 Interactive Exercises
- 0 Assessments
- 10 Cubes
Module Description
Looking to learn the fundamentals of reverse engineering? Look no further than our Reverse Engineering module! This comprehensive module will teach you the basics of reverse engineering, including how to analyze and deconstruct software and systems to understand their inner workings. With a focus on practical applications, you'll leave the module with the skills and knowledge necessary to tackle real-world reverse engineering challenges.
Module Summary
The Reverse Engineering module is designed for students or enthusiasts who are interested in learning more about reverse engineering, either as a potential career path or as a personal interest, Cybersecurity professionals who want to enhance their skills in vulnerability assessment, penetration testing, and malware analysis, and IT professionals who want to gain a deeper understanding of how computer systems work, or who are interested in enhancing their skills in cybersecurity and system administration. Throughout this module, students will develop an understanding of the principles of reverse engineering and how it can be applied in software, hardware, and systems analysis, how to analyze and interpret low-level code and data structures, including assembly language, machine code, and binary formats, and practice reverse engineering on real-world examples, using a hands-on, problem-based approach to learning.
Recommended prior knowledge:
Basic programming skills in at least one programming language, such as Python, C, or Java
A basic understanding of computer architecture and digital logic
Familiarity with computer systems and operating systems, including the command line interface
Sections
8 sections - 1 Interactive
| # | Group | Type | Title |
|---|---|---|---|
| 1 | None | theory | Preliminary Information about Reverse Engineering Fundamentals Course |
| 2 | theory | Introduction to Reverse Engineering | |
| 3 | theory | Reverse Engineering Basics | |
| 4 | theory | Basic Concepts | |
| 5 | theory | Memory Layout | |
| 6 | theory | Sample C Program | |
| 7 | interactive | C Binary Decompiling with Ghidra | |
| 8 | theory | Reverse Engineering Quiz |
Conclusion
In this module, we covered the fundamentals of reverse engineering including compiling versus decompiling source code, the distinction between stack and heap memory, endianness (big-endian and little-endian byte ordering), using ILSpy to decompile .NET C# binaries back to readable source code, and using Ghidra to analyze compiled C binaries through its disassembler and decompiler views.
Module key takeaways:
- Compilers translate high-level source code into machine code; decompilers attempt the reverse, reconstructing pseudo-source from binary instructions with varying accuracy
- The stack stores local variables and return addresses in LIFO order and is managed automatically by push/pop instructions; the heap stores dynamically allocated memory managed by the programmer
- Little-endian systems (x86/x64) store the least significant byte at the lowest address; understanding endianness is essential when reading raw bytes from memory dumps or network captures
- ILSpy decompiles .NET assemblies by reading the Common Intermediate Language (CIL) bytecode, often recovering near-original C# code including class structures and method names
- Ghidra's CodeBrowser presents a synchronized disassembly and decompiler view, enabling analysts to rename variables, retype data, and annotate functions to reconstruct program logic
- Identifying imported library functions (such as CreateFile, WriteFile, or connect) in the binary's import table quickly reveals what capabilities a program has
- String extraction from binaries often yields hardcoded paths, registry keys, C2 URLs, and error messages that guide deeper analysis