Dynamic Analysis
Due Date: 2026-11-09 23:59:59
Submission: via GitLab repo
- Due Date: 2026-11-09 23:59:59
- Submission: via GitLab repo
- Introduction
- Setup
- Part 1: Dynamic Analysis
- Part 2: Written Analysis
- Submission
Introduction
Dynamic analysis involves executing a sample in a controlled environment and observing its runtime behavior. You will use system call tracing, network capture, and sandbox tooling to characterize what a sample does when it runs.
Safety requirements
- Revert to your clean VM snapshot before each sample
- Disable or isolate the VM’s network interface before executing anything
- Take a new snapshot immediately before running each sample so you can compare before/after state
Setup
Obtain the samples from ada.cs.pdx.edu:/stash/malware_re/dynamic/:
$ scp -r <MCECS>@ada.cs.pdx.edu:/stash/malware_re/dynamic/ ~/malware/samples/hw3/
That directory holds three binaries, and only two of them are graded work:
bombandbomb2are this assignment. Defuse both, and write up both.bomb3is not part of the homework. It is the bomb used in the pwndbg dynamic-analysis walkthrough, shipped prebuilt so you can follow that page without compiling it yourself. Expect the literal addresses on that page to differ from the ones you see — it says as much, and shows you the command that looks up yours. Read the walkthrough in full if you like; it gives away none of the graded work. Nothing you do withbomb3is submitted or graded.
Do not confuse the two sets. A report that analyzes bomb3 instead of bomb
and bomb2 has analyzed the practice bomb and answered none of the questions
asked here.
Part 1: Dynamic Analysis
You should have two sample files to work on, bomb and bomb2. Using the debugger of your choice, run the programs and determine the solutions to defuse the bomb. If you don’t have an x86 linux machine on which to run the files, I would suggest you make use of ada or babbage to run this code.
The programs are non-malicious, and therefore do not pose a risk to your system.
I would suggest using tools designed for this process, such as:
You must do this exercise entirely dynamically! We won’t be mixing the tools until next time around.
Part 2: Written Analysis
Write a 1–2 page analysis report covering each sample, documenting:
- the debugger and tooling you used, and how you set it up,
- your approach to obtaining the solution,
- what the program does,
- the breakpoints, watchpoints, and memory reads that actually got you the information you needed — show the evidence, not just the conclusion,
- how you were able to generate the solution, and
- the dead ends. A bomb that detonated is part of the analysis; say what you learned from it.
Screenshots are both appreciated and encouraged. An very thorough example style can be seen in this crackme reverse engineering writeup.
Submission
Commit and push hw3/hw3.md with all findings, screenshots from your debugging session, and your written analysis. Include any scripts that you wrote to solve the challenges in the repo as well.