PDF malware analysis — malicious · 23bfd0f8d4c7aabc

MALICIOUS

PDF

25.3 KB Created: 2011-72-51 03:25:00 Authoring application: String.fromCharCode

MD5: 4b76c7f70784f81f267b7d0b63e5120b SHA-1: c16a45af9c3b5bc7e6e9be69c62a02d556750922 SHA-256: 23bfd0f8d4c7aabcc10438fd7a4c87a2677dad3a17a0105c5d64d4eedd55b6da

64 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 Command and Scripting Interpreter: PowerShell

The PDF file contains embedded JavaScript, indicated by multiple heuristic firings including 'PDF_JAVASCRIPT', 'PDF_JS', and 'PDF_METADATA_EVAL_STAGER'. The 'String.fromCharCode' usage suggests obfuscation. The primary function of the embedded JavaScript appears to be a stager, designed to decode and execute further malicious code, likely from an external source. No specific malware family is identifiable from the available evidence.

Heuristics 4

PDF metadata JavaScript eval stager high PDF_METADATA_EVAL_STAGER

PDF JavaScript reads document metadata fields such as title, subject, or producer, decodes character data with parseInt/String.fromCharCode style helpers, and evals the recovered stage. This is a high-signal exploit-kit staging pattern.
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.
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.

Extracted artifacts 1

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`javascript_obj0001_000.js` `df8af9cbfb36f953c51054d5d8926d4744d19f5722a954aa21fc4a65bc738b9e`	pdf-javascript-stream	PDF /JS object 1 at offset 0x6267	536 bytes

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