Malicious RTF — malware analysis report

Static analysis result for SHA-256 c00019e41e123292…

MALICIOUS

RTF

242.7 KB First seen: 2020-02-04
MD5: 9a12defcc9d67c28a04037363e0b0762 SHA-1: 985809201445b9cb30517461f5fbc3ad5c81b7bf SHA-256: c00019e41e1232928aa341e16fb1088d93ceda02ec225a1bbf3292611deb7075
120 Risk Score

Malware Insights

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

The RTF file contains OLE object data that is force-activated via \objupdate, indicating exploitation of CVE-2017-0199 or CVE-2017-8759. This mechanism is used to load a second-stage payload from the OLE moniker stream. The specific vulnerabilities exploited are identified as CVE-2017-0199 and CVE-2017-8759.

Heuristics 3

  • CVE-2017-0199 / CVE-2017-8759 (OLE2Link auto-activated remote loader) critical CVE related RTF_OLE2LINK_REMOTE_MONIKER_LOADER
    RTF embeds an OLE2Link object that is force-activated with \objupdate (no user interaction on open) and fetches a remote second stage — through an INCLUDETEXT/INCLUDEPICTURE field or the OLE object's own moniker. This is the OLE2Link auto-update attack path shared by CVE-2017-0199 (server returns an HTA/scriptlet) and CVE-2017-8759 (server returns a SOAP WSDL the .NET parser compiles). Office processes the fetched response through the same code path; the specific CVE depends on the now-unreachable server content type.
  • \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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000003c.bin rtf-objdata-decoded RTF \objdata at offset 0x3C 2608 bytes
SHA-256: c667c1d923492a52a6e2e32f5290f130e1df208df5f758f1f40ec435fc3cf6a0