Malicious PDF — malware analysis report

Static analysis result for SHA-256 3ca8c514c385f690…

MALICIOUS

PDF

26.2 KB
MD5: 0c2c5ffe59f26c2e1c7fbe5051b1eaea SHA-1: 461aa01a6f1716ff8525207d5dd374ae7ac72d0f SHA-256: 3ca8c514c385f690a51c25eec967d205c97a81b7ef08e6287b49d0375934d2ea
156 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File T1566.002 Spearphishing Attachment

The PDF file contains embedded XFA forms with risky executable scripts, indicated by high-severity heuristics like PDF_XFA_SCRIPT and PDF_EMBEDDED_SCRIPT_PAYLOAD. The presence of unescape() and String.fromCharCode() calls suggests JavaScript obfuscation, commonly used to hide malicious code that likely downloads and executes a second-stage payload. An embedded file artifact was also detected. The confidence is high due to multiple strong indicators, but the family is unknown as no specific indicators pointed to a known variant.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

Heuristics 8

  • 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.
  • unescape() call high PDF_UNESCAPE
    unescape() found — often used to decode shellcode in PDF JS exploits
  • 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.
  • 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.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://ns.adobe.com/xdp/
    • http://www.xfa.org/schema/xfa-template/2.5/
    • http://www.xfa.org/schema/xfa-data/1.0/

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_file_obj0008.bin
3faa754d540cffac8b9ba2a5174419348cf7feafd2151c66bc71c0eca0fd6f33		 pdf-embedded-file PDF EmbeddedFile object 8 at offset 0xC6 26145 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).

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