Malicious RTF — malware analysis report

Static analysis result for SHA-256 6ebfe024e89c7899…

MALICIOUS

RTF

1.52 MB Created: 2019-09-17 13:59:00 First seen: 2020-06-01
MD5: f865f2bcbd9739c133b9052cf76eebfb SHA-1: 47779c74d21a22e13d69db00e8df4a68cfbd4368 SHA-256: 6ebfe024e89c78998ea3372544e854a632d23872d826dffe5d9756ae2a5997d2
142 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 is configured to update via \objupdate, triggering exploitation of CVE-2017-8759. This vulnerability allows for the activation of the OLE object, which is a common method for downloading and executing secondary payloads. The presence of the benign URL is likely a decoy or part of the exploit chain.

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_off00178c0c.bin rtf-objdata-decoded RTF \objdata at offset 0x178C0C 1413 bytes
SHA-256: bbf8ce5789a07f26d0e06ee30b3adeb99077a208d9c3974952a22999e1646fd2

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