Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 0fb7ae512f4ef34b…

MALICIOUS

Office (OLE)

185.0 KB Created: 2007-09-18 04:34:00 Authoring application: Microsoft Word 11.
MD5: 4a9f48b8e29a6ac4a00730719aad97ef SHA-1: 39ba3897c6597e4ef11ccff43cba44fab4ea4600 SHA-256: 0fb7ae512f4ef34bba0f16cb401cb5d1daa95061ca5fe7e202e34aedbd818f9e
140 Risk Score

Malware Insights

MITRE ATT&CK
T1027 Obfuscated Files or Information T1566.001 Spearphishing Attachment

The sample exhibits high slack space and an appended executable payload, strongly suggesting it's a dropper. The presence of XOR-encoded strings further indicates an attempt to obfuscate malicious content. While no specific family is identified, the techniques point to a malicious document designed to deliver a secondary payload.

Heuristics 3

  • XOR-encoded strings (key 0xFC) critical SC_XOR_ENCODED
    Found 5 Windows library/API name(s) XOR-encoded with single-byte key 0xFC: 'LoadLibraryA', 'GetProcAddress', 'VirtualAlloc', 'CreateProcessA', 'RegOpenKeyExA'
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 189,440 bytes but its declared streams total only 16,486 bytes — 172,954 bytes (91%) 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).
  • OLE file has appended executable-looking payload bytes high OLE_APPENDED_PAYLOAD
    OLE compound file contains a large high-entropy region beyond the declared major streams and that region includes shellcode, PE, or loader API markers. This is a payload-carrier signal, not a specific CVE attribution by itself.

Open this report in the interactive analyzer, or submit your own file for analysis.