Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 7ba8bf5281fe910e…

MALICIOUS

Office (OLE)

1.18 MB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: acae77021edc3f0342b317bb3675971e SHA-1: 547ba902425f69c779d854d129807ea144a0a397 SHA-256: 7ba8bf5281fe910ec14c62a82b35319a53b88a842213e5383a2018c310f5bd78
142 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The file is an Excel document exhibiting significant anomalies, including a large slack space and an appended executable payload. Crucially, it triggers a critical heuristic for CVE-2009-3129, a known Excel vulnerability allowing for arbitrary code execution. This exploit is likely used to download and run a secondary payload, although no specific URLs for this are present in the provided evidence.

Heuristics 4

  • CVE-2009-3129 — Excel FEATHEADER record overflow critical CVE exact CVE_2009_3129
    Workbook BIFF stream contains a FEATHEADER (Feature Header) record with anomalous size (record_size=23, isf=2, cbHdrData=4294967295). Legitimate FEATHEADER records are tiny (<100 bytes) and carry cbHdrData values that fit in the record body; the value here is the documented CVE-2009-3129 exploit primitive — cbHdrData drives a memcpy with attacker-controlled size, leading to memory corruption and code execution in Excel 2007/2003.
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 1,235,416 bytes but its declared streams total only 24,565 bytes — 1,210,851 bytes (98%) 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.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://ns.adobe.com/xap/1.0/
    • http://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://ns.adobe.com/iX/1.0/
    • http://ns.adobe.com/exif/1.0/
    • http://ns.adobe.com/pdf/1.3/
    • http://ns.adobe.com/photoshop/1.0/
    • http://ns.adobe.com/tiff/1.0/
    • http://ns.adobe.com/xap/1.0/sType/ResourceRef#
    • http://ns.adobe.com/xap/1.0/mm/
    • http://purl.org/dc/elements/1.1/
    • http://www.iec.ch

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