Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 90b0ccc50def6b56…

MALICIOUS

Office (OLE)

108.8 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: b95f91db2648df2cdb1d070013ce7dc4 SHA-1: 20e745e67516417c9e38fa18eee3dcbd40584290 SHA-256: 90b0ccc50def6b56e82bd85a778640536e83f2e385708f18efd05691853c024a
180 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution T1059.003 Command and Scripting Interpreter: Windows Command Shell

The critical CVE-2009-3129 heuristic indicates this Excel file exploits a known vulnerability to achieve code execution. The suspicious cmd.exe invocation suggests the exploit is used to launch a command-line process, likely for downloading additional malware. The large slack space in the OLE structure is also a common characteristic of exploit documents. While no specific family is identified, the combination of exploit and command execution points to a downloader or initial access stage.

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 111,422 bytes but its declared streams total only 24,565 bytes — 86,857 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).
  • 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.