Malicious RTF — malware analysis report

Static analysis result for SHA-256 276ce2b4bbaa8e5c…

MALICIOUS

RTF

181.9 KB Created: 2019-09-08 16:28:00 First seen: 2020-05-25
MD5: fda7ea88d08778977149964b404d11db SHA-1: a4fc177cac4a44fca72f6da57c6e4891fa412200 SHA-256: 276ce2b4bbaa8e5c49b8d4a10bf27b4d771660b344dbbe5c094d7ff0318e2dc4
142 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects that are triggered via \objupdate, leading to the exploitation of CVE-2017-8759. This vulnerability allows for the activation of MSXML SAX OLE objects, which can lead to arbitrary code execution. The document body is heavily obfuscated and does not provide clear textual lures.

Heuristics 5

  • 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.
  • \objupdate forces OLE activation high RTF_OBJUPDATE
    RTF contains \objupdate — forces automatic OLE object instantiation when the document is opened, bypassing user interaction. Almost exclusively seen in Equation Editor exploit documents.
  • 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/office/word/2003/wordml In RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0001d59d.bin rtf-objdata-decoded RTF \objdata at offset 0x1D59D 25542 bytes
SHA-256: e76b40f14f288a43386398e1d6d638544e0ebde0d56fdbd7c3dbefab3fdba4da

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