Malicious PDF — malware analysis report

Static analysis result for SHA-256 bcdb1cac045a1c02…

MALICIOUS

PDF

118.4 KB
MD5: a8b6a329687b7a2986958559a87d2c1d SHA-1: ce977153d9b3434edb2517619721bb8693deb73c SHA-256: bcdb1cac045a1c02641a9cad377a326df8f00e2fc07d04f33ffcd4ed2949a359
166 Risk Score

Malware Insights

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

The PDF contains embedded JavaScript, with high-confidence heuristics indicating the use of eval() and a large comment-padded JavaScript eval stager. ClamAV detection as 'Pdf.Exploit.Agent-36086' strongly suggests an exploit is present. The obfuscated nature of the JavaScript and the lack of readable document body text prevent a more specific determination of the payload or exact exploit mechanism, but the overall pattern points to a malicious PDF designed to deliver an exploit.

Heuristics 7

  • ClamAV: Pdf.Exploit.Agent-36086 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Pdf.Exploit.Agent-36086
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution (matched inside decoded stream)
  • Large comment-padded JavaScript eval stager high PDF_JS_LARGE_COMMENT_PADDED_EVAL
    PDF JavaScript contains a very large stream padded with long random-looking block comments around String.fromCharCode and eval. This is an exploit-kit obfuscation shape used to bury a decoder and recovered stage inside noise, not normal PDF form automation.
  • 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_obj0006_000.js
edc4339b6d521e387ddb562dadb1de43e2fb423766c45e0684bfbaa5b2568604
pdf-javascript-stream PDF /JS object 6 at offset 0x143 626657 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s). Carved artifact contains 42 long base64-like blob(s).
legacy_pdfkit_stage_000.js
cda6bf0c869e2e0cddd2acba3a7edcff5a8b12d606438a8ebbac920affdd13d0
deobfuscated-js double percent-decoded annotation JavaScript at offset 0x143 262144 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 620 long base64-like blob(s).