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

Static analysis result for SHA-256 0fb0c0d674324fe5…

MALICIOUS

Office (OLE) / .DOC

98.5 KB Created: 2005-06-29 18:14:00 Authoring application: Microsoft Word 10.0
MD5: 6c04b138da483852e0f28143bbd5f1cc SHA-1: 49cedf92a11d8aa3b244a1ccfc155da34f04334e SHA-256: 0fb0c0d674324fe509cd13bf7ed0ca6a4e74fb29b1b044309186ebed677e548b
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1105 Ingress Tool Transfer

The OLE document exhibits anomalies including a large slack region and appended payload bytes, indicating it's a dropper. The presence of an embedded URL further supports the hypothesis that this file is intended to download and execute a secondary stage payload. No scripts were extracted from this sample.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 100,864 bytes but its declared streams total only 20,632 bytes — 80,232 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.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://www.tibet.ca/en/newsroom/library/tsg_faq