Malicious PDF — malware analysis report

Static analysis result for SHA-256 4203a555dd48ac74…

MALICIOUS

PDF

11.8 KB
MD5: 4d37e67bc2789d10904aa2ce3a718db2 SHA-1: 05a3987579fbc713ee90be41ce5ce7f1313353cf SHA-256: 4203a555dd48ac74b406cbd08544bb1c39e1b7b0d46717bd147e159320d29d55
126 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript that is obfuscated and uses String.fromCharCode, indicating an attempt to hide malicious code. The critical heuristic CVE_2007_5659 specifically identifies the use of Collab.collectEmailInfo to exploit a vulnerability, leading to the execution of a JavaScript stager. This stager is designed to download and execute a second-stage payload, characteristic of a malicious document dropper.

Heuristics 6

  • 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)
  • Annotation subject callee-key hex JavaScript stager high PDF_ANNOT_SUBJECT_CALLEE_HEX_STAGER
    PDF JavaScript uses syncAnnotScan()/getAnnots() to read an indirect annotation /Subject stream, percent-decodes it through marker replacement, then uses a callee.toString()-derived key to decode and eval the final exploit stage.
  • 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_obj0007_000.js
c860bd3a1b8438b37e98a599719a1868ae540624631f091272ffef48912644f4
pdf-javascript-stream PDF /JS object 7 at offset 0x19C 579 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 eval/decoder/string-building token(s).
annotation_subject_callee_hex_stage_000.js
4775590b41524b04aa49e32114e83d21aa8b91b22e19fb27217d224fe94d565b
deobfuscated-js annotation-subject callee-key decoded JavaScript at offset 0x14A 5187 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 5 eval/decoder/string-building token(s).