PDF / .TMP malware analysis — malicious · d913367754f6ea4d

MALICIOUS

PDF / .TMP

90.7 KB Created: mPF 013×OÐvö¯¨/uÒ,Kà First seen: 2026-05-10

MD5: 47a5b25c4fa967f3180bbe4091bc423a SHA-1: e84ef2a29d1d0c9cc4cf380ce8a28a942ab239dd SHA-256: d913367754f6ea4d0825a22b143dd6bad39926163e83367f8edf2aced1888d64

152 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 JavaScript

The PDF was flagged as suspicious due to the presence of embedded JavaScript, which is used to conceal its encrypted content. This technique is commonly employed to evade detection and deliver malicious payloads. The JavaScript action and embedded JS stream indicate that the script is integral to the file's functionality, likely for obfuscation or to execute further malicious code.

Machine Learning

Nyx PDF Classifier malicious score 0.9997

Heuristics 7

JavaScript action low 2 related findings PDF_JAVASCRIPT

PDF contains a /JavaScript action. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
PDF JavaScript exploit cluster critical PDF_JS_EXPLOIT_CLUSTER

PDF combines an executable JavaScript/action surface with exploit staging indicators such as eval/unescape/fromCharCode, XFA script content, or a related CVE pattern. Benign form JavaScript remains low-severity, but this correlated cluster is high-confidence malicious behavior.
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.
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.
Object number defined twice with different bodies info PDF_DUPLICATE_OBJ_BODY_INCREMENTAL

The same indirect object (N G) is defined more than once with different body bytes. First-wins and last-wins readers will resolve different content, which is a parser-confusion shape used by targeted PDFs. Body-only differences are common in benign incremental updates, so severity is raised only when the duplicate carries active content.
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://www.cadkas.com In PDF document text

Extracted artifacts 2

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`javascript_obj0026_000.js`	pdf-javascript-stream	PDF /JS object 26 at offset 0x99C3	42 bytes
SHA-256: `76e21958c55cd739dc2b69ddc0b41e5d5cf8ff3ddaccfc6393f1aec9622bde05`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 2 eval/decoder/string-building token(s).
Preview script First 1,000 lines of the extracted script eval("eval(\""+getField("e").value+"\")");
`javascript_obj0032_000.js`	pdf-javascript-stream	PDF /JS object 32 at offset 0x1FFC	42 bytes
SHA-256: `7f13760feb01564b86f2c3838599aa2c37d677be563ce2ce871d12e66b84c815`
Preview script First 1,000 lines of the extracted script � �fٴŒ�� O��\. X��ڼ[=� �b7 �� ~Ԣ

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