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

Static analysis result for SHA-256 427c6c6226be74ed…

MALICIOUS

Office (OLE) / .DOC

118.0 KB
MD5: 492b69182aa9f50c59e51c57efd7e4fe SHA-1: 491c899166b468559a0f0deafec3eda2cd3055d9 SHA-256: 427c6c6226be74ed48cb876339b57ff6742c5cb4ebedab83ea5417c847af303d
82 Risk Score

Malware Insights

MITRE ATT&CK
T1559.001 Component Object Model Hijacking

The file is an OLE document with a significant amount of slack space and embedded EMF objects, indicating a potential for malicious content delivery. The 'Unsupported Office format for VBA extraction' heuristic suggests that standard macro analysis was not possible, but the presence of embedded objects points towards an attack pattern involving their exploitation. The document body contains references to embedded Excel and PowerPoint objects, further supporting this.

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 120,832 bytes but its declared streams total only 31,351 bytes — 89,481 bytes (74%) 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.