Malicious RTF — malware analysis report

Static analysis result for SHA-256 12544960d69cfa9a…

MALICIOUS

RTF

2.47 MB First seen: 2019-04-18
MD5: e1a7e6805643c66ad9ca7b4d88834463 SHA-1: b546eba4feef6f1e0405bce6b535780b675a4667 SHA-256: 12544960d69cfa9a6c596c21bc97e73f78d7934b70bc24688457c002dad7e186
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains OLE object data that is force-activated via \objupdate, triggering a remote loader vulnerability (CVE-2017-0199 or CVE-2017-8759). This mechanism is used to download and execute a second-stage payload from an embedded OLE moniker stream. The specific second-stage payload and its ultimate destination could not be determined statically.

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_off001be49f.bin rtf-objdata-decoded RTF \objdata at offset 0x1BE49F 4270 bytes
SHA-256: b1eac5f62b11ad4357d0834656f42d75466e16c97c359f89bd7e5aa3efada64e