Malicious RTF — malware analysis report

Static analysis result for SHA-256 c71c88f460daf48f…

MALICIOUS

RTF

2.70 MB Created: 2021-06-07 05:35:00 First seen: 2021-06-13
MD5: 809b9ef61aa79700bc211600c4f56ab5 SHA-1: a09abcfeb66402fe7db35fda8bc2a89386ba51d4 SHA-256: c71c88f460daf48f08873ff155a1e344f2e1dc3e8642f340b8c10d8a5f901959
302 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains a critical heuristic firing for CVE-2017-8759, indicating exploitation of MSXML SAX OLE activation. Additionally, high-severity heuristics detected an embedded OLE package object with excessive hex data, containing a PE header, strongly suggesting it's a dropper. The document body's prompt to 'Enable Content' further supports a malicious intent to execute embedded code.

Heuristics 8

  • CVE-2017-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759
    RTF contains a hex-encoded OLE1 object for Msxml2.SAXXMLReader.6.0 followed by an embedded OLE compound document, and the document requests OLE activation. This matches the RTF staging shape used for CVE-2017-8759 SOAP/WSDL parser code injection.
  • ClamAV: Rtf.Dropper.Agent-9965975-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Rtf.Dropper.Agent-9965975-1
  • PE header (with DOS stub) in hex data critical RTF_MZ_HEX
    Hex-encoded PE (MZ + DOS stub) found inside RTF — likely an embedded executable payload
  • Package object class high RTF_OBJCLASS_PACKAGE
    OLE Package object — can wrap arbitrary files
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~2639KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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://schemas.microsoft.com/offi In RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off002889a6.bin rtf-objdata-decoded RTF \objdata at offset 0x2889A6 43747 bytes
SHA-256: d2450f0595519ebe40595c8f4f6edfac87aa784aa8702395671d3b50a814ff45

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