Malicious PDF — malware analysis report

Static analysis result for SHA-256 7a2c3297ee6817d2…

MALICIOUS

PDF

26.5 KB
MD5: e54accb6b93a2ea641fbc1c13601e284 SHA-1: 893a00509de8f8279485af05157c6a57bf331dec SHA-256: 7a2c3297ee6817d2e2612e626caa08638fa9eb29104d86345fadec498de4e421
158 Risk Score

Malware Insights

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

The PDF file contains XFA forms with risky executable scripts, indicated by high-severity heuristics like PDF_XFA_SCRIPT and PDF_UNESCAPE. The ML classifier strongly flags this as malicious. The embedded file and script payload suggest the document is designed to deliver a secondary exploit or payload, likely leveraging obfuscation techniques like unescape() and String.fromCharCode() to evade detection. The specific intent of the script is unclear due to obfuscation, but it is designed to execute malicious code.

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
a92f5752961bd606a5b6ed01a14032ced87e97c07a39205e85dbc1b923af6680		 pdf-embedded-file PDF EmbeddedFile object 8 at offset 0xC6 26373 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.