Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 3edede42afa978b0…

MALICIOUS

Office (OLE)

177.8 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: 72cd7a98fc3e1cd11796889ffc6321cb SHA-1: 1bad5c7ccc091cb9056970319c198a53bb3cae81 SHA-256: 3edede42afa978b0138539b50cd83912bb0249f7a5e49199cf46d097d39586d5
82 Risk Score

Malware Insights

MITRE ATT&CK
T1553.005 Mark-of-the-Web Bypass T1027 Obfuscated Files or Information

The OLE document exhibits a large slack space and an appended executable payload, indicating it's likely a container for malicious code. The high entropy of the appended bytes suggests obfuscation. Although VBA macros could not be extracted due to an unsupported format, the presence of an appended payload strongly suggests the file's purpose is to deliver malware. The SHA256 hash is included as a primary IOC.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 182,117 bytes but its declared streams total only 24,565 bytes — 157,552 bytes (87%) 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.