Malicious PDF — malware analysis report

Static analysis result for SHA-256 a281bbf33b002f95…

MALICIOUS

PDF

96.7 KB Created: 2017-09-24 17:12:40 -05:00 Authoring application: Microsoft® Word 2016 First seen: 2021-01-23
MD5: 22f1a79e7b61042cf49b3c2bd8c14ee6 SHA-1: faf29b4f719e072b639acf396885df9038817893 SHA-256: a281bbf33b002f95aceba7c74dd39c793976745a82b8f1ef0daafef564c7449e
96 Risk Score

Machine Learning

  • Nyx PDF Classifier malicious score 0.7352

Heuristics 5

  • Image-only PDF lure links to a brand-impersonating path on an unrelated host high PDF_IMAGE_LURE_BRAND_PATH_LINK
    PDF is image-heavy with little real text and its clickable action targets a URL carrying a brand name ('docusign') as a path segment on a host that does not belong to that brand and is not known-good (e.g. 'sodecoperu.com/Docusign/index.php'). This is the credential-phishing carrier shape where a compromised or unrelated host serves a brand-named phishing kit behind a screenshot-like lure page. Distinct from the typosquat-host rule: here the host is honest-looking but the brand lives in the path.
  • 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 96 KB — typical shape of a phishing lure where a full-page screenshot hides a clickable button that launches or submits to an attacker URL.
  • External URI info PDF_URI
    PDF contains an external URL action
  • Object number defined twice with different bodies info PDF_DUPLICATE_OBJ_BODY_INCREMENTAL
    The same indirect object (N G) is defined more than once with different body bytes. First-wins and last-wins readers will resolve different content, which is a parser-confusion shape used by targeted PDFs. Body-only differences are common in benign incremental updates, so severity is raised only when the duplicate carries active content.
  • 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 https://telegramacantado.com.br/docuSign/ PDF link annotation
    • https://telegramacantado.com.br/document/docuSignIn PDF document text
    • https://telegramacantado.com.br/doc/docuSignIn PDF document text
    • https://ecoen.agnesscott.org/document/docuSign/In PDF document text
    • https://tom-jeff.com/document/docuSignIn PDF document text
    • https://kolobernining.com/b/doc/docuSignIn PDF document text
    • http://kolobernining.com/b/doc/docuSignIn PDF document text
    • https://telegramacantado.com.br/docuSign/)/SIn PDF document text
    • https://telegramacantado.com.br/doc/docuSign)/SIn PDF document text
    • https://kolobernining.com/b/doc/docuSign)/SIn PDF document text
    • http://kolobernining.com/b/doc/docuSign)/SIn PDF document text
    • http://www.w3.org/1999/02/22-rdf-syntax-ns#In PDF document text
    • http://purl.org/dc/elements/1.1/In PDF document text
    • http://ns.adobe.com/xap/1.0/In PDF document text
    • http://ns.adobe.com/pdf/1.3/In PDF document text
    • http://ns.adobe.com/xap/1.0/mm/In PDF document text
    • http://www.aiim.org/pdfa/ns/extension/In PDF document text
    • http://www.aiim.org/pdfa/ns/property#In PDF document text
    • http://www.aiim.org/pdfa/ns/schema#In PDF document text
    • http://www.aiim.org/pdfa/ns/id/In PDF document text

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