Malicious PDF — malware analysis report

Static analysis result for SHA-256 8e48beed6c120934…

MALICIOUS

PDF

139.8 KB Created: 2016-08-04 10:01:52 +00:00 Authoring application: 377376M(Foxit Advanced PDF Editor) (via 376377000M000i000c000r000o000s000o000f000t000256000 000W000o000r000d000 0002000000010006)
MD5: e4945fd9438c01a020efcbdba2e7b030 SHA-1: 6e221d304fa72d6b5945dd5cc786fa689210d7af SHA-256: 8e48beed6c1209342c42e1815c6c3bf29d3f34d77f144961faa5fe0cc88ba9d8
150 Risk Score

Malware Insights

MITRE ATT&CK
T1566.002 Phishing: Spearphishing Attachment T1204.002 Malicious Link

The PDF is identified as an image-only lure, a common phishing technique to disguise malicious links. The heuristic 'PDF_IMAGE_LURE_SHORTENER_LINK' specifically points to a URL shortened via bit.ly, indicating an attempt to obscure the final destination. ClamAV detection further confirms its malicious nature as 'Pdf.Dropper.Agent-7281649-0'. The document body is heavily obfuscated and contains no readable text, reinforcing the idea that the visual presentation and the embedded link are the primary attack vectors.

Machine Learning

  • Nyx PDF Classifier malicious score 0.6214

Heuristics 4

  • ClamAV: Pdf.Dropper.Agent-7281649-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Pdf.Dropper.Agent-7281649-0
  • Image-only PDF lure links through URL shortener high PDF_IMAGE_LURE_SHORTENER_LINK
    PDF is image-heavy with little real text and its clickable action points to a URL shortener. This is a high-confidence credential-phishing carrier shape: the visible page is a screenshot-like prompt while the destination is hidden behind redirect infrastructure.
  • Image-only document with action trigger (screenshot lure) medium PDF_IMAGE_LURE
    PDF has 2 image(s), only 0 text block(s), carries a click-outward action, and is only 139 KB — typical shape of a phishing lure where a full-page screenshot hides a clickable button that launches or submits to an attacker URL.
  • 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.w3.org/1999/02/22-rdf-syntax-ns#
    • http://ns.adobe.com/pdf/1.3/
    • http://purl.org/dc/elements/1.1/
    • http://ns.adobe.com/xap/1.0/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://bit.ly/2hTLt8m

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