Malicious PDF — malware analysis report

Static analysis result for SHA-256 2609e8c0890ff031…

MALICIOUS

PDF

25.5 KB Created: 2011-72-51 03:25:00 Authoring application: String.fromCharCode
MD5: 4bd56f337904ca3fd3bf3bd97d2f426d SHA-1: 5d4e6008b8a7bd2732304cf6b4d56091a08ea717 SHA-256: 2609e8c0890ff031ffb0438b6aabb390079fc2fb9a822a327d9268ddd5250be5
64 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File

The PDF file contains JavaScript embedded within its metadata, triggered by the 'PDF_METADATA_EVAL_STAGER' heuristic. The use of 'String.fromCharCode' suggests obfuscation techniques common in JavaScript-based malware. This script likely acts as a stager to download and execute a secondary payload, although the specific URL or payload could not be determined from the static analysis.

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
fe26f6dba42e315a1109cffb52312b933e7eab090a46e4d3b20ae8290a3522a7
pdf-javascript-stream PDF /JS object 1 at offset 0x62D4 537 bytes