Malicious PDF — malware analysis report

Static analysis result for SHA-256 eb76c0ceaa596ed3…

MALICIOUS

PDF

118.6 KB
MD5: 9cacfdac0a8e90308c63094260cdfaed SHA-1: 31ff84e7159bde34599dc706ea237f8cff9ecc1a SHA-256: eb76c0ceaa596ed300b717aedc5a99d04449a8755b8833d31c26f45600043390
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, indicated by multiple heuristic firings including 'PDF_JAVASCRIPT', 'PDF_JS', and 'PDF_EVAL'. The 'PDF_JS_LARGE_COMMENT_PADDED_EVAL' heuristic specifically points to a stager designed to execute code. ClamAV detection as 'Pdf.Exploit.Agent-36086' further confirms its malicious nature. The primary attack pattern involves leveraging JavaScript within the PDF to initiate a malicious action, likely downloading and executing further malware.

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.

FilenameKindSourceSize
javascript_obj0006_000.js
a44d647eb8030ddc9e3f6a6be77b78a1edf566415b55e542b4bcffba378b13be
pdf-javascript-stream PDF /JS object 6 at offset 0x143 627564 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).