Malicious PDF — malware analysis report

Static analysis result for SHA-256 25886d0635ffd223…

MALICIOUS

PDF

9.5 KB
MD5: 75ac1b74a7bb0b6a438084dfe0d4c0c8 SHA-1: 6e1e1dd581bf086008b18e63283147a930f797bf SHA-256: 25886d0635ffd2230034b1df95dd4cc15a03fb82f8f08cc28b8479ec93d2be51
126 Risk Score

Malware Insights

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

The PDF file contains high-severity heuristics indicating the presence of risky executable scripts within XFA forms, along with embedded file content. The deobfuscated JavaScript payload is likely responsible for executing the embedded file, which is a common technique for delivering second-stage malware. The exact functionality of the script is not fully discernible due to potential obfuscation, but its presence strongly suggests a malicious intent to download and execute further payloads.

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
e8ee79f0cf0b7b94f8a217cbcfb16722f0e2a663d458a77cf24a845e7f19ab7a
pdf-embedded-file PDF EmbeddedFile object 41 at offset 0x52 1164 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).
deobfuscated.js
d7483bbee884d59b6ffd570083c136ecb5927bea2b97e83e045002819a12a226
deobfuscated-js PDF JavaScript deobfuscation pass 2349 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).