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

Static analysis result for SHA-256 4727f3f5b87e787c…

MALICIOUS

Office (OLE) / .DOC

75.5 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: fc349adc24f9f597a3a5059ec51627db SHA-1: 41f6dbf92d45ce3310cc1f0892eb51d06aea2026 SHA-256: 4727f3f5b87e787ceda44a8b64b7cdcbc3073653be8ec3b49346225cd32a7a8a
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The OLE document exhibits anomalies indicative of a malicious payload, including a large slack region and appended executable-looking bytes. While VBA macros could not be extracted due to an unsupported format, the presence of an embedded URL suggests a social engineering attempt. The file's SHA256 hash is provided as a primary IOC.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 77,312 bytes but its declared streams total only 16,543 bytes — 60,769 bytes (79%) 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.