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

Static analysis result for SHA-256 763872737e7836d7…

MALICIOUS

Office (OLE) / .DOC

82.5 KB Created: 2009-02-26 07:53:00 Authoring application: Microsoft Office Word
MD5: ea79b4e4cf6c0462f477d1ca1e1402b5 SHA-1: 2cf0b1c09bf8b9b458deb65dcef693e8d8f44e03 SHA-256: 763872737e7836d72196156be5337eca791c856ead290263bc365c8834db5e0c
140 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The sample is an OLE document with a significant portion of its data being an appended payload, indicating it is likely a dropper. The XOR-encoded strings suggest obfuscation techniques are in use to hide malicious functionality. The document body is minimal, providing no specific lure, but the overall structure points to a malicious attachment designed to deliver a secondary payload.

Heuristics 3

  • XOR-encoded strings (key 0xC2) critical SC_XOR_ENCODED
    Found 2 Windows library/API name(s) XOR-encoded with single-byte key 0xC2: 'advapi32.dll', 'RegOpenKeyExA'
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 84,484 bytes but its declared streams total only 16,543 bytes — 67,941 bytes (80%) 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.