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

Static analysis result for SHA-256 e9f198b95d1a125a…

MALICIOUS

Office (OLE) / .XLS

107.0 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: 28d560f70ec8364f407956bf079f15d7 SHA-1: ee80fec2884c038b000a56f12b7b97acfd4db7ca SHA-256: e9f198b95d1a125ab6857d185ade7d5cfd7a91c5b02b547e378a9237b9afcdf1
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.002 Spearphishing Attachment T1027 Obfuscated Files or Information T1105 Ingress Tool Transfer

Static analysis revealed significant anomalies in the OLE structure, including a large unaccounted-for region and an appended executable payload. The 'OFFICE_FORMAT_UNSUPPORTED' heuristic indicates that VBA macros could not be extracted, suggesting potential obfuscation or a legacy format. The presence of an appended payload strongly suggests this file is a dropper or downloader for further malicious activity.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 109,592 bytes but its declared streams total only 24,565 bytes — 85,027 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.