Malicious PDF — malware analysis report

Static analysis result for SHA-256 ecea34302034d9b4…

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: e36c73f8af292f287d58093eb087923f SHA-1: 46bd979c3bfaa7e27c22c2e392c60f8e0efebc58 SHA-256: ecea34302034d9b4c6bf18d26e3477d1fbe2eb35fe9509bc9917b98940a38701
166 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 JavaScript/JScript T1204.002 Malicious File

The PDF file contains embedded JavaScript triggered by the OpenAction, which is a known technique for exploiting PDF reader vulnerabilities. The critical CVE_2007_5659 heuristic indicates the use of Collab.collectEmailInfo with a decoded JavaScript string that is evaluated. This suggests the script is designed to download and execute a secondary payload. No specific family could be identified, but the technique is common for initial access.

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
aedc69a85a286f27c1518600e70a9421aa2578b4d6146100a2e73cde8208b3ba
pdf-javascript-stream PDF /JS object 13 at offset 0x3D7 13543 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
7a717985f42c719b7e6fbdcd644a457d8a42ab82162ea907e36b15a018bcb880
deobfuscated-js numeric char-code string decoded JavaScript at offset 0x445 4044 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 5 eval/decoder/string-building token(s).