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

Static analysis result for SHA-256 73d17706c36f3957…

MALICIOUS

Office (OLE) / .XLS

102.3 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: 4453a9b549231343e023231477a35f4c SHA-1: b125b5daf832059403020b05ead2093e80aadced SHA-256: 73d17706c36f395712dccf2b490ebd32a272ae1de434d8d34ed79e94d9fc4e56
180 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File T1059.003 Windows Command Shell

The sample is an Excel file that triggers a critical heuristic for CVE-2009-3129, indicating an exploit for a known Excel vulnerability. High severity heuristics for PEB access and suspicious cmd.exe invocation suggest post-exploitation activity. The OLE slack anomaly further points to a malformed or intentionally packed structure. While no scripts were extracted, the presence of embedded URLs and the exploit technique strongly suggest the file's purpose is to download and execute a malicious payload.

Heuristics 5

  • 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=22, isf=4, cbHdrData=4). 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.
  • PEB access via FS segment (x86) high SC_PEB_ACCESS
    PEB access via FS segment (x86)
  • Suspicious cmd.exe invocation with execution flag high SC_STR_CMD
    Suspicious cmd.exe invocation with execution flag
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 104,766 bytes but its declared streams total only 24,565 bytes — 80,201 bytes (77%) 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).
  • 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://www.pdf-repair.com
    • http://www.pdf-repair.com)/Producer(Advanced
    • http://www.pdf-repair.com)/ModDate(D:20100406171120+08
    • http://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://ns.adobe.com/pdf/1.3/
    • http://ns.adobe.com/xap/1.0/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://purl.org/dc/elements/1.1/

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