Malicious RTF — malware analysis report

Static analysis result for SHA-256 309e22ca759d8db0…

MALICIOUS

RTF

219.3 KB Created: 2019-12-02 11:55:00 First seen: 2020-09-04
MD5: ba6dc04e8cff6410da747a5593eb7c26 SHA-1: 869904825597e4f6382300de088e818c5d24b7ed SHA-256: 309e22ca759d8db0f6fb5b1b55e09af56f76a5a7f5608424711597b26969aaee
142 Risk Score

Malware Insights

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

The RTF file contains multiple embedded OLE objects and triggers an OLE activation via \objupdate, which is a strong indicator of exploitation. The critical heuristic firing for CVE-2017-8759 confirms the exploitation of this specific vulnerability to achieve code execution. The embedded benign URL is not considered a malicious IOC.

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 3 \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 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002cd3.bin rtf-objdata-decoded RTF \objdata at offset 0x2CD3 19003 bytes
SHA-256: 6041c4cfc8e570dd412030a065aac2b7cadb1c1950215e5ddd93eb6b6e29f554
objdata_02_off000208e1.bin rtf-objdata-decoded RTF \objdata at offset 0x208E1 19003 bytes
SHA-256: 71ec3ad328ee6544257ac8790e2a38785ba37c16da606b52e7febb33c0976404