Malicious PDF — malware analysis report

Static analysis result for SHA-256 d931590898bee200…

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: 111c90cf3f39bd4519d350aba1642380 SHA-1: 130cadaa90b26e837de8bc43d99d3e9b34c50119 SHA-256: d931590898bee20071224fb4ce6540b3e96f0a3e0f4bea3910f8232f9302364d
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 common technique for exploiting PDF readers. The critical CVE_2007_5659 heuristic indicates the use of Collab.collectEmailInfo with a numeric character-code string to decode JavaScript. This JavaScript is then evaluated, suggesting it's designed to download and execute a secondary payload. The presence of obfuscated JavaScript streams further supports this malicious intent.

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
f4ebc283c7190fd2c97c3b33050f8f81825d409b594e96e4fd7f2c5706128c90
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
6d960af47ef58a90e0d6451386702c0c6ed7bb06b63510821489fff573362646
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).