Malicious PDF — malware analysis report

Static analysis result for SHA-256 a6452524f3eca43d…

MALICIOUS

PDF

15.7 KB Created: 2009-11-15 19:41:70 Authoring application: PDF Library 4.3.9 (via PDF Library 3.9.7)
MD5: 3f65ed2cfe0c2e57501b230222986acf SHA-1: 5a6a8d66043ca1aabacba167807e2bb6eefe52fb SHA-256: a6452524f3eca43df8972be29ed58d38e24b97ffd1b2a5c230c65d4e4a039a8b
136 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript, indicated by the PDF_JAVASCRIPT and PDF_JS heuristics. ClamAV detections (Pdf.Dropper.Agent-7290006-0 and Win.Trojan.Agent-36166) confirm its malicious nature, classifying it as a dropper. The embedded JavaScript is likely responsible for downloading and executing the secondary payload, which is a common technique for such droppers. The document body was unreadable, so the rationale is based on the heuristics and extracted artifact names.

Heuristics 4

  • ClamAV: Pdf.Dropper.Agent-7290006-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Pdf.Dropper.Agent-7290006-0
  • ClamAV detection on extracted artifact critical EXTRACTED_FILE_CLAMAV
    ClamAV flagged at least one file extracted from inside this sample. Even when the wrapping document carries no AV detection of its own, a hit on the carved artifact is a strong indicator the sample is a delivery vehicle.
  • 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.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
javascript_obj0007_000.js
e9bd60964da0cc7e0dd27e361f37cadc1ac9371453fbc1f3c766595767801827		 pdf-javascript-stream PDF /JS object 7 at offset 0x1A5 81994 bytes
Detection
ClamAV: Win.Trojan.Agent-36166
Obfuscation or payload: unlikely

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