Malicious PDF — malware analysis report

Static analysis result for SHA-256 4a2a5c5c43457c38…

MALICIOUS

PDF

3.6 KB Created: 2008-31-20 53:85:00 Authoring application: Scribus 1.3.3.12 (via Scribus PDF Library 1.3.3.12)
MD5: 2df8cae42320dfc30a47e70edc65cb60 SHA-1: 0c7a82d435496ea54935ffbff45fd2bd8fc41432 SHA-256: 4a2a5c5c43457c38b3bd7d536ecd765c4af9eed48117f6de3a741e3824ddd7dd
168 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript that is triggered by the OpenAction. Heuristics indicate the use of eval() and String.fromCharCode, along with a critical finding for CVE-2007-5659 (Collab.collectEmailInfo). This suggests the JavaScript is obfuscated and likely decodes and executes a malicious payload. The extracted JavaScript files, particularly 'numeric_charcode_stage_000.js', are indicative of a multi-stage attack designed to download and execute further malware.

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