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

Static analysis result for SHA-256 c4b97d9cbc42dd4f…

MALICIOUS

Office (OLE) / .DOC

135.5 KB
MD5: 3246e4c5207e1e0d760e4b4c94dd73b7 SHA-1: a9c700b0ce8a4d51cce3410db769e53efd4dee5f SHA-256: c4b97d9cbc42dd4ff4703105b14d3bd4bb2ef4bdb5f41801fdb1960eabc47f5f
82 Risk Score

Malware Insights

MITRE ATT&CK
T1559.001 Component Object Model Hijacking

The OLE document exhibits anomalies in its structure, including a large slack space and an EMF object within an EPRINT stream, suggesting malicious intent. Although VBA macros could not be extracted, the presence of embedded object references like 'Excel.Sheet.8' and 'PowerPoint.Slide.8' within the document body indicates an attempt to exploit OLE embedding mechanisms. The document body itself is a report about test file construction, likely a lure to encourage interaction with the embedded objects.

Heuristics 3

  • Office EPRINT stream contains EMF object high CVE related OLE_EPRINT_EMF_OBJECT
    OLE ObjectPool contains an EPRINT stream with EMF data. This is rare in normal documents and is CVE-2007-3893/MS07-046-family evidence when paired with Office exploit payload anomalies, but the malformed EMF record is not proven by this rule alone.
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 138,752 bytes but its declared streams total only 31,351 bytes — 107,401 bytes (77%) 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).
  • 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.