Malicious PDF — malware analysis report

Static analysis result for SHA-256 db66cca7e99e0a65…

MALICIOUS

PDF

9.5 KB
MD5: 135a2f34461dafea196b575822966904 SHA-1: eb0784254a45ed402c2882d8390885636c39740b SHA-256: db66cca7e99e0a65d5678cd75ded157a136795ba3f8cbd6d5775cfce82713d29
156 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution: Malicious File T1059.007 Command and Scripting Interpreter: JavaScript

The PDF file contains XFA forms with executable scripts, indicated by high-severity heuristic firings like PDF_XFA_SCRIPT and PDF_EVAL. The embedded JavaScript file 'deobfuscated.js' is likely responsible for executing the malicious payload. The ML classifier strongly flags this PDF as malicious, supporting the conclusion that it's designed for exploitation and payload delivery.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

Heuristics 7

  • XFA form contains risky executable script high CVE related PDF_XFA_SCRIPT
    PDF embeds an XFA form whose script block contains exploit, submission/launch, or shell-execution primitives. Ordinary LiveCycle print/update scripts are left as generic XFA/JS signals unless stronger behavior is present.
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution (matched inside decoded stream)
  • Embedded script payload in PDF stream medium PDF_EMBEDDED_SCRIPT_PAYLOAD
    PDF stream bytes contain an HTML/XFA <script> tag without accompanying Windows shell-execution primitives — common in accessible XFA forms but worth surfacing for analyst review.
  • Embedded file low PDF_EMBEDDED
    PDF embeds a file attachment — could carry an executable or another weaponised document as a nested payload
  • XFA form low PDF_XFA
    PDF uses XML Forms Architecture — can contain script logic
  • 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
embedded_file_obj0041.bin
bfdc89a64dae169c5dec5f03dcda977c1e1dafafe12bd3b2d35032b9ee609fce
pdf-embedded-file PDF EmbeddedFile object 41 at offset 0x52 1163 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).
deobfuscated.js
3b3e057b2b3cf8d5b43edcdc1d664998c25227d05f77ce2a600c06402b4da0b4
deobfuscated-js PDF JavaScript deobfuscation pass 1733 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).