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

Static analysis result for SHA-256 05170ed1515c87e6…

MALICIOUS

Office (OLE) / .DOC

124.0 KB
MD5: a5019ed431314a4055ee0009812cd360 SHA-1: 718e57b1cb5d4fc6f3dda1436a2256cb5d4d6144 SHA-256: 05170ed1515c87e65a871396f37b5b9d1db7ac6bf920051b295d4d18d69f3352
80 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits significant slack space and an appended executable payload, strongly suggesting it is designed to deliver a secondary malicious file. The presence of these anomalies points towards a dropper functionality, likely delivered via spearphishing.

Heuristics 2

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 126,976 bytes but its declared streams total only 12,338 bytes — 114,638 bytes (90%) 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.