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

Static analysis result for SHA-256 980c78fa7823e2f6…

MALICIOUS

Office (OLE) / .XLS

107.0 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: e062a6c102e007072745925c2983b067 SHA-1: 45d3874af8c612f328709b5ea191c7c3f95ef8b2 SHA-256: 980c78fa7823e2f6021f5e805823eab20b9a885b2c43a428e00389ef8309fc8c
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The OLE document exhibits characteristics of malicious intent, including a large unaccounted-for region and an appended executable payload with high entropy. Although VBA macros could not be extracted due to an unsupported format, the presence of these anomalies strongly suggests the file is designed to deliver malware. The appended payload is the primary indicator of 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.