Malicious PDF — malware analysis report

Static analysis result for SHA-256 f7e31e19bbf3ef28…

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: d9921cf1e0350a4b07a0bc2ee0488d26 SHA-1: 0183d1f7d89e297693704da49af229e7aa35751d SHA-256: f7e31e19bbf3ef28499ab259dcd1db2aadff55149ce2d96b50aca15250cfb52a
166 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript that is triggered by the OpenAction feature, indicating an attempt to exploit a vulnerability. The critical CVE-2007-5659 heuristic firing confirms the use of a known exploit targeting PDF readers. The embedded JavaScript, particularly the use of eval() and String.fromCharCode, suggests obfuscation and dynamic code execution, likely to download and execute a secondary payload. No specific family could be identified.

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
81b1ad7ff1ddb5ac7214d4732b4703a0fc7773bc3b7023cd418d1a4e9bdadd77
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
b642fc13024dfe0b9ee72f684d28bef600246b645a2edf48ebd4679a14647c83
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).