PDF malware analysis — malicious · 78cd5cbddbbb3b52

MALICIOUS

PDF

15.7 KB

MD5: 6e321d1f33709d725d78675052f156ff SHA-1: 9b43daa49b239f5bcc536e8c2615fb92ec0326fc SHA-256: 78cd5cbddbbb3b52717536f79cb6b8d852eb908ff14fedd3fa43be1a12a546c7

166 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 JavaScript/JScript T1204.002 Malicious File

The PDF file contains embedded JavaScript, indicated by multiple heuristic firings including 'PDF_JAVASCRIPT', 'PDF_JS', and 'PDF_JS_LARGE_COMMENT_PADDED_EVAL'. The critical 'CLAMAV_DETECTION' rule further confirms its malicious nature. The embedded JavaScript stream, named 'javascript_obj0006_000.js', is likely responsible for executing the exploit and downloading a secondary payload, as suggested by the 'PDF_EVAL' and 'PDF_FROMCHARCODE' heuristics. The document body is unreadable, but the presence of JavaScript and the ClamAV detection strongly suggest an exploit delivery mechanism.

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 1

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`javascript_obj0006_000.js` `387d07f189edef3d0f64c41e88abeea7fb2502c6157f745c432232781b0db8ca`	pdf-javascript-stream	PDF /JS object 6 at offset 0x143	424869 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).

Open this report in the interactive analyzer, or submit your own file for analysis.