Malicious Office (OLE) / .DOC — malware analysis report

Static analysis result for SHA-256 1f0325db6ad179df…

MALICIOUS

Office (OLE) / .DOC

403.0 KB Created: 2007-12-03 01:19:00 Authoring application: Microsoft Word 9.0
MD5: 19a7686ef6a992f157e2108ca5df2f01 SHA-1: 68b12dc11e58ad355d96dfb77c8d0c48b2fc55ca SHA-256: 1f0325db6ad179dfe08f7099340b845a1902246abe303a9f878515fa31f3cae1
140 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The sample is an OLE document with significant slack space and a detected NOP sled, indicating potential shellcode. The XOR-encoded strings suggest obfuscation commonly used to hide malicious payloads. While an embedded URL was found, it was confirmed as benign. The lack of a document body or scripts limits the ability to determine the exact attack pattern or family, but the heuristics point towards a downloader or exploit delivery mechanism.

Heuristics 4

  • XOR-encoded strings (key 0x95) critical SC_XOR_ENCODED
    Found 2 Windows library/API name(s) XOR-encoded with single-byte key 0x95: 'LoadLibraryA', 'GetProcAddress'
  • NOP sled detected high SC_NOP_SLED
    Found 20+ consecutive 0x90 bytes
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 412,721 bytes but its declared streams total only 16,486 bytes — 396,235 bytes (96%) live in unallocated sector slack. This is the canonical hiding place for pre-macro-era Office exploit payloads (XOR-encoded shellcode reached via a parser pointer-corruption bug in the document structure).
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://schemas.microsoft.com/office/word/2003/wordml}}\paperw11909\paperh16834\margl1774\margr526\margt1087\margb709\gutter0\ltrsect