Malicious PDF — malware analysis report

Static analysis result for SHA-256 c3336cabccc6d65a…

MALICIOUS

PDF

76.8 KB
MD5: 7b825e48a4b8a230222dc39d76082ca0 SHA-1: a18f40b948afa50720c9ded491b05eaa97b6039a SHA-256: c3336cabccc6d65abcca1b0797cd998d20ed549c3d946b23a1f66c29abe992f0
166 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.001 Malicious Link T1204.002 Malicious File

The PDF file contains embedded JavaScript that utilizes a binary-XOR stager to decode and execute a second-stage payload. The critical heuristic firing CVE_2007_5659 indicates the exploitation of a known Adobe Reader vulnerability (CVE-2007-5659) via the `Collab.collectEmailInfo` method. The JavaScript is heavily obfuscated using string concatenation and XOR operations, typical of exploit delivery mechanisms.

Heuristics 7

  • Collab.collectEmailInfo — CVE-2007-5659 critical CVE exact CVE_2007_5659
    PDF JavaScript calls Collab.collectEmailInfo — CVE-2007-5659 is a buffer overflow in Adobe Reader triggered by a long argument or heap-sprayed message field passed to Collab.collectEmailInfo(). Part of a series of Acrobat JS API exploits. (identified after JavaScript deobfuscation)
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution
  • Binary-XOR JavaScript stager high PDF_BINARY_XOR_JS_STAGER
    PDF JavaScript stores viewer-version payload branches as long binary digit strings, XORs each bit pair, converts 8-bit chunks with String.fromCharCode, and evals the recovered exploit stage.
  • JavaScript action low PDF_JAVASCRIPT
    PDF contains a /JavaScript action. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
  • Embedded JS stream low PDF_JS
    PDF references a /JS stream. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
  • String.fromCharCode low PDF_FROMCHARCODE
    String.fromCharCode found — used to construct payload strings dynamically. Common in benign JavaScript libraries for codepoint manipulation, so this alone is informational; weaponised use is also caught by the dedicated fromCharCode-stage and exploit-shape rules.
  • Suspicious extracted artifact info EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
javascript_obj0004_000.js
374311c1020ae818c209ecf9de4a2723ffe21c0135e4f3782e213eceba6d9b9c
pdf-javascript-stream PDF /JS object 4 at offset 0xC0 78298 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 3 eval/decoder/string-building token(s). Carved artifact contains 6 long base64-like blob(s).
binary_xor_stage_000.js
3dc12132d42ce8f06536a07f9ef9df4161599025495e9c99b61d5352d61e9ee6
deobfuscated-js binary-XOR decoded JavaScript at offset 0x3D7 1285 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 3 eval/decoder/string-building token(s).