Malicious PDF — malware analysis report

Static analysis result for SHA-256 7bedff27493af20d…

MALICIOUS

PDF

25.2 KB Created: 2011-72-51 03:25:00 Authoring application: String.fromCharCode
MD5: 8a66325a2631d2adef802c99dad52946 SHA-1: 9f257b66b0895c5afda8142e0ef526f6e66979f4 SHA-256: 7bedff27493af20d2d7fdd62b6fff78ad7366af262255271e358016486fc8e87
64 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 Command and Scripting Interpreter: PowerShell

The PDF file contains embedded JavaScript, identified by the 'PDF_METADATA_EVAL_STAGER' heuristic, which is designed to decode and execute a payload. The use of String.fromCharCode further indicates obfuscation techniques common in malicious PDFs. The primary attack vector appears to be leveraging JavaScript execution within the PDF metadata to achieve initial compromise.

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.

FilenameKindSourceSize
javascript_obj0001_000.js
1490235fcf990da6a7094ce48570baed1771e13e8b3e41818c4378b1e35d989e
pdf-javascript-stream PDF /JS object 1 at offset 0x620E 524 bytes