Malicious RTF — malware analysis report

Static analysis result for SHA-256 2d2b28cec47ed559…

MALICIOUS

RTF

6.2 KB First seen: 2019-09-30
MD5: d5d54a150eff6b25b4199d9afb96f022 SHA-1: b4b4743da644c90af75255eedbf463f39c5bb1ab SHA-256: 2d2b28cec47ed559c55f25f346528bb2b4f88a3ec4cfc67bf7d8cc1968017b92
120 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object that triggers the CVE-2017-8759 vulnerability. This vulnerability is known to be used for remote code execution, typically to download and execute a second-stage payload. The presence of the ".bin" file and the specific heuristic firings strongly indicate this exploit is being leveraged.

Heuristics 3

  • SOAP Moniker — CVE-2017-8759 (SOAP WSDL RCE) critical CVE related CVE_2017_8759
    RTF \objdata decodes to OLE data containing the SOAP Moniker — CVE-2017-8759 (SOAP WSDL RCE) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
  • \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 3132 bytes
SHA-256: 2662e7567a9bad6eb6571929f9658882480e05d77b97e9361a95dc6adf5a0189

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