Case 184E5D · Malware & intel · L2 Practitioner
Triaging an unknown binary
Interview questionSomeone hands you a suspicious executable from a user's laptop. Walk me through how you work out what it does.
- 01 Answer
- 02 Example
- 03 Trade-offs
What a strong answer covers
Try it out loud first. Then check yourself:
- Handle safely: hash it, store it zipped with a password, analyse only in an isolated VM with snapshots and no corporate network
- Static first: file type, PE headers, signer, compile time, imports, strings and entropy (packed?), YARA and hash reputation
- Dynamic: detonate in a sandbox or VM with Procmon, Sysmon and fake DNS/HTTP to capture files, registry, processes and C2
- Example: a fake installer that drops to AppData, adds a Run key and beacons to a young domain; hand those IOCs to the SOC
- Trade-offs: uploading to public VirusTotal can tip off the actor; sandboxes miss evasive samples; go deep only if it matters
If the interviewer pushes back
- The sample does nothing in your sandbox. What are the likely reasons and how do you get it to run?