MALICIOUS
262
Risk Score
Malware Insights
MITRE ATT&CK
T1203 Exploitation for Client Execution
The critical CVE-2009-3129 heuristic indicates exploitation of a Microsoft Excel vulnerability. High severity heuristics for NOP sleds, PEB access, and suspicious cmd.exe invocation suggest the execution of malicious code. The presence of an appended executable payload further supports this, likely leading to the download and execution of a second-stage payload via cmd.exe, potentially involving PowerShell.
Heuristics 7
-
CVE-2009-3129 — Excel FEATHEADER record overflow critical CVE exact CVE_2009_3129Workbook 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.
-
NOP sled detected high SC_NOP_SLEDFound 20+ consecutive 0x90 bytes
-
PEB access via FS segment (x86) high SC_PEB_ACCESSPEB access via FS segment (x86)
-
Suspicious cmd.exe invocation with execution flag high SC_STR_CMDSuspicious cmd.exe invocation with execution flag
-
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALYOLE file is 191,038 bytes but its declared streams total only 24,565 bytes — 166,473 bytes (87%) 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_PAYLOADOLE 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_URLOne 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.