Malicious PDF — malware analysis report

Static analysis result for SHA-256 30d3770b80bd4029…

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: bb4d0000df33cb44ecffe72ee8ebe5a5 SHA-1: e0cc567c5a8926557798e448ca83b694b7df821f SHA-256: 30d3770b80bd4029f4aa77908344074815529dcdbea63068505a0784ebe50cd9
166 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 JavaScript T1204.001 Malicious Link T1059.003 Windows Command Shell

The PDF file contains embedded JavaScript that is triggered by the OpenAction. Heuristics indicate the use of eval() and String.fromCharCode, suggesting obfuscated JavaScript execution. Specifically, the CVE-2007-5659 technique was identified, which involves exploiting a vulnerability to collect email information and execute decoded JavaScript. This script likely downloads and executes a second-stage payload.

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
94d7021be1e03b2af53ec4393488ee9f9286e1627576bc379ab0275093efc731
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
91e98775d90cfbdcffc703919c67dbb39f33244f6971adff8c61e2580ef2db82
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).