PDF malware analysis — malicious · 35d36a1a6268ba4e

MALICIOUS

PDF

118.5 KB

MD5: e21fa381bb4d94e3765c3bd156969c5d SHA-1: 6f9338190ad31f478193473e9108235346c5a0e5 SHA-256: 35d36a1a6268ba4efa4adfaab46c94a10835d210bf903cb6e48effa114df5a0b

196 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 PowerShell T1204.002 Malicious File

The PDF contains embedded JavaScript, including a large comment-padded eval stager. This JavaScript is obfuscated and uses eval() and String.fromCharCode(), indicating it's designed to execute malicious code. ClamAV detected this file as 'Pdf.Exploit.Agent-36086', strongly suggesting it's an exploit delivery mechanism. The ML classifier also flagged it with high confidence. The primary attack pattern involves leveraging JavaScript within the PDF to achieve code execution, likely for downloading and running further malicious content.

Machine Learning

Nyx PDF Classifier malicious score 1.0000

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` `ac15729d3b1240812279eeed3fff3b031630cfd94cc0f6670e7c4a99eb5d0f92`	pdf-javascript-stream	PDF /JS object 6 at offset 0x143	627139 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.