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

Static analysis result for SHA-256 21ae007fae56a282…

MALICIOUS

Office (OLE) / .XLSX

4.10 MB
MD5: 771bf0441f701a4df4aa4161487ffa92 SHA-1: 924b6b3cd0bff4ce884fcc131ea7df99ac220d8f SHA-256: 21ae007fae56a2823d0ea730141dbaca5192304aad9d781197518a003ae7284a
80 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The OLE document exhibits a significant slack space anomaly and contains appended executable payload bytes. This suggests the file is designed to deliver a secondary malicious payload. As the document content is encrypted, the specific lure or delivery method cannot be determined from the body.

Heuristics 2

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 4,293,988 bytes but its declared streams total only 2,540,876 bytes — 1,753,112 bytes (41%) 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.

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