PDF malware analysis — malicious · 7f1766bd625c8ca1

MALICIOUS

PDF

15.7 KB

MD5: 87f5d88fa398bdc84675df396d721fda SHA-1: 5061100947102bee4f60396aa7b3fb2befb26a98 SHA-256: 7f1766bd625c8ca130e4e5f764bba0f92f0541dc21fc0a851392dde31be568b5

166 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 PowerShell T1204.002 Malicious File T1566.001 Spearphishing Attachment

The PDF file contains embedded JavaScript that utilizes `eval()` and `String.fromCharCode()`, indicating an attempt to obfuscate malicious code. The presence of `PDF_JAVASCRIPT`, `PDF_JS`, and `PDF_EVAL` heuristics, along with a critical ClamAV detection for 'Pdf.Exploit.Agent-36086', strongly suggests this is a malicious PDF designed to exploit vulnerabilities. The embedded JavaScript streams, particularly the large comment-padded eval stager, are indicative of a downloader or stager mechanism, likely intended to fetch and execute further malicious content.

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.

Filename	Kind	Source	Size
`javascript_obj0006_000.js` `c4ab1c1314df9f0502f13546dfe37eab448541ac590fc74445bb3ec69bb83bdf`	pdf-javascript-stream	PDF /JS object 6 at offset 0x143	425238 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` `663b9071b11607c69426d62b9ce80076056015ad10085093e992b66ae4df9ce2`	deobfuscated-js	double percent-decoded annotation JavaScript at offset 0x143	262144 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 426 long base64-like blob(s).

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