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

Static analysis result for SHA-256 1fe758e761e2760c…

MALICIOUS

Office (OLE) / .XLS

126.3 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: 157be0d62d421f0f3b8fd744ece5db53 SHA-1: ef136615729a8c7e6eba3e2295e5a3c5b16fa395 SHA-256: 1fe758e761e2760c8afc6dd5f13ef58e5e00a6792254bc5452208b6f7c8c1166
180 Risk Score

Malware Insights

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

The sample is an Excel file that exploits CVE-2009-3129, a known vulnerability in Microsoft Excel's FEATHEADER record. The heuristic firings indicate suspicious command-line execution and PEB access, suggesting the exploit is used to download and execute a second-stage payload. The embedded URLs, while not definitively malicious, are associated with a domain that warrants further investigation.

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 129,342 bytes but its declared streams total only 24,565 bytes — 104,777 bytes (81%) 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.