Malware Analysis: Runtime Linking in a Sample with No Imports
· 7:49 · Watch on YouTube ↗
Summary
The video introduces runtime linking through analysis of a malware sample with no static imports or useful strings, showing how analysis tools help identify runtime-resolved function pointers and related behavior.
Key points
- Runtime linking lets malware resolve operating-system functionality at runtime rather than relying on a conventional import directory.
- The sample is described by the presenter as actual malware; its hash is shown, but no hash value is present in the supplied transcript.
- Initial triage finds a valid PE file with no imports and few useful strings.
- FLOSS identifies stack strings, while Kappa reports behaviors including loader-data access, resolving functions through PE exports, and XOR-encoding data.
- IDA analysis shows global variables initialized to zero that appear to be populated at runtime and used as function pointers.
Article Details
- Topics
- [00:00] Runtime linking and its role in malware
- [01:02] Selecting the sample and beginning basic triage
- [02:05] Examining the sample's missing imports and limited strings
- [03:33] Using FLOSS to identify stack strings
- [04:10] Kappa capability analysis and runtime-linking clues
- [05:07] Using IDA to trace runtime-populated function pointers
