Malicious PDF — malware analysis report

Static analysis result for SHA-256 837abf6e19d1f0e1…

MALICIOUS

PDF

3.5 KB Created: 2008-31-20 53:85:00 Authoring application: Scribus 1.3.3.12 (via Scribus PDF Library 1.3.3.12)
MD5: 08a78bc03f36c840861903f64d6deba0 SHA-1: de60dad4f13ab99e818e2781817488f6b41857ba SHA-256: 837abf6e19d1f0e11da8ffdf0b417106531f963d0ceda16e403526795cf67049
166 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript triggered by the OpenAction, which is a known technique for exploiting PDF vulnerabilities. The critical heuristic firing for CVE-2007-5659 indicates the use of `Collab.collectEmailInfo` to decode and evaluate JavaScript. This script likely downloads and executes a second-stage payload, as suggested by the presence of deobfuscated JavaScript streams and the overall malicious verdict.

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)
  • OpenAction trigger high PDF_OPENACTION
    PDF has an /OpenAction — code runs automatically when opened
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution (matched inside decoded stream)
  • 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. (matched inside decoded stream)
  • 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_obj0013_001.js
ba9a3a5f3806114eb891d4e3abea9e4d3cccf6bd9baa0f31e007c74a55d345be
pdf-javascript-stream PDF /JS object 13 at offset 0x3D7 13289 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 3 eval/decoder/string-building token(s).
numeric_charcode_stage_000.js
5e08d36af0574c2ece1308f7ab802442486e68470a8cc8a724589cf14c4530ba
deobfuscated-js numeric char-code string decoded JavaScript at offset 0x445 4032 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 5 eval/decoder/string-building token(s).