PDF malware analysis — malicious · adeacf1e06741a22

MALICIOUS

PDF

22.46 MB

MD5: 8b8b29b005867320e54f1fa7f4a6e2b6 SHA-1: c79fa38ab85b9a2c35364ed01dc3540a50d734a2 SHA-256: adeacf1e06741a22fb09f2670a1503a16a94f99e0fcb79599979b3af6da3e793

134 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 JavaScript T1566.003 Phishing: Spearphishing Attachment T1190 Exploit Public-Facing Application

The PDF file exhibits multiple high and medium severity heuristic firings indicating malicious intent. Specifically, the 'PDF_ENCRYPTED_WITH_JS' and 'PDF_FILTER_HEX' rules suggest that JavaScript is used to hide and potentially exploit content within the document. The 'PDF_PRC_3D' finding further points to the use of advanced, potentially exploitable features. The presence of JavaScript actions and embedded JS streams strongly suggests that the document is designed to execute code, likely to download and execute a second-stage payload.

Heuristics 8

PRC/3D content in PDF high CVE related PDF_PRC_3D

PDF contains PRC 3D content. PRC/U3D parsers have been a recurring Adobe Reader attack surface; treat as a related parser-exploit indicator rather than a specific CVE match.
Encrypted PDF carries /JavaScript — payload hidden from static analysis high PDF_ENCRYPTED_WITH_JS

PDF declares /Encrypt and also references an executable trigger (/JavaScript). Document encryption hides the JavaScript body and stream contents from static scanners — combined with auto-execution indicators this is a known evasion pattern used to deliver weaponised JavaScript that the analyst cannot inspect without the decryption key.
ASCIIHexDecode filter (with exploit indicators) medium PDF_FILTER_HEX

Hex-encoding filter present alongside exploit delivery indicators — often used to hide payload or shellcode bytes
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.
XFA form low PDF_XFA

PDF uses XML Forms Architecture — can contain script logic
Additional-actions dictionary low PDF_AA

PDF defines /AA (Additional Actions) that references an executable action (JS/JavaScript/Launch/SubmitForm) — can auto-trigger on document or widget events. Form-field calc/format/validate/keystroke handlers in legitimate interactive forms commonly fire this, so it is reported as a low-weight signal; weaponised auto-execution is flagged by stronger rules (PDF_OPENACTION, encrypted-with-JS, etc.)
PDF paints image(s) but contains no text operators info PDF_IMAGE_ONLY_LURE

PDF has 2 image XObject(s) and the content stream contains no text-emitting operators (BT/ET, Tj, TJ, ', ") in either raw bytes or decompressed streams — this is the screenshot-as-PDF pattern used to bypass text-based scanners and to deliver instructions purely through rendered pixels. It is informational unless paired with invisible links or risky URI context.

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