Using PE-Sieve to Unpack and Analyze Packed Executables in Memory
· 11:35 · Watch on YouTube ↗
Summary
A malware-analysis lesson demonstrates using PE-Sieve to dump a suspended packed process from memory, then explains alignment, import-table, and entry-point issues that remain when analyzing the unpacked code.
Key points
- PE-Sieve scans a selected process for memory modifications and can dump modules with realignment.
- The demonstration suspends a process after its behavior changes, such as making a request in FakeNet, to improve the chance that unpacked code is present in memory.
- The speaker verifies that the dumped executable contains previously hidden strings and examines its sections and code.
- A memory dump may retain packing artifacts, have an unresolved import table, and still point to the packer's entry point rather than the original entry point.
- The lesson presents memory dumping as a useful starting point, while noting that further work is needed to make the sample easier to analyze in IDA Pro.
Article Details
- Topics
- [00:12] Packed executables in memory and using PE-Sieve to scan and dump a process
- [01:28] Suspending a process at a useful point during unpacking
- [03:04] Recognizing when unpacked behavior is present and running PE-Sieve
- [04:39] Reviewing the dumped module and section alignment
- [06:28] Verifying unpacked strings and examining UPX artifacts
- [08:20] Import-table and original-entry-point limitations in further analysis
People
Tools
FakeNet[02:10] select something in Fakenet because wehxd[05:17] So, take a look at this in HxD.IDA Pro[00:00] All right, before we dive into IDA Pro,PE-sieve[00:27] called PE Sieve. This is a tool bySystem Informer[04:14] here using a tool like System Informer,YARA[09:35] Maybe if you're using a tool like Yara
