Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 1d9acc4f0c937abc…

MALICIOUS

Office (OLE)

172.5 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: acadc11b9fe5f8d7c29f74cbd42caffb SHA-1: 8625c41492e0c8e337ae6df879d51c7db53bb725 SHA-256: 1d9acc4f0c937abc987cdbc6a7b6eace7fe2c6af17644ff4c51e282b3b96b80b
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE file exhibits a large slack region and appended executable-looking payload bytes, indicating it's likely a dropper. Although VBA macros could not be extracted due to an unsupported format, the presence of appended payload strongly suggests malicious intent. The file's SHA256 hash is included as a primary IOC.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 176,640 bytes but its declared streams total only 16,543 bytes — 160,097 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.
  • Unsupported Office format for VBA extraction info OFFICE_FORMAT_UNSUPPORTED
    olevba could not extract VBA macros (PermissionError); format-agnostic byte-level scans still ran. Likely legacy, encrypted, or malformed OLE/OOXML — re-scanning the same bytes will yield the same outcome.

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