Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 b760de4df6d70976…

MALICIOUS

Office (OLE)

73.3 KB Created: 2008-07-11 06:57:00 Authoring application: Microsoft Office Word
MD5: 1f536c57f64c88a46af6bd38637c2aa2 SHA-1: 3cfc209c2c4e2bf14ea942d5307f78d149656008 SHA-256: b760de4df6d70976544d239a29578bad321e53bee83a0d2eb3039266b6cfedac
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The OLE file exhibits anomalies including a large unaccounted-for region and appended executable-looking payload bytes. While VBA macros could not be extracted due to an unsupported format, the presence of appended payload strongly indicates a malicious intent to deliver malware. The SHA256 hash of the file is provided as an IOC.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 75,018 bytes but its declared streams total only 16,543 bytes — 58,475 bytes (78%) 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.

Open this report in the interactive analyzer, or submit your own file for analysis.