RTF malware analysis — malicious · 8d36b83e80032ba7

MALICIOUS

RTF

471.6 KB Created: 2019-07-17 01:21:00 First seen: 2019-09-30

MD5: 83bbe5e2a5242de93eb546e4ef22c6fc SHA-1: 300c9b54a3747925d7dc5457cbfb93f2f8c2a4ee SHA-256: 8d36b83e80032ba7dea7138a71bd4ea10aeb3c2ad00565b809c023aafa158479

144 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple embedded OLE objects, with heuristics indicating that \objupdate forces OLE activation. Crucially, the CVE-2017-8759 heuristic fires, pointing to exploitation of MSXML SAX for OLE activation. This suggests the file is designed to execute arbitrary code, likely by downloading and running a second-stage payload.

Heuristics 6

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 4 \objdata section(s) — embedded OLE objects
Embedded OLE object medium RTF_OBJEMB

RTF contains \objemb — embedded OLE object
Suspicious extracted artifact info EXTRACTED_FILE_STATIC_TRIAGE

One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
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 4

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00002937.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x2937	45121 bytes
SHA-256: `af9ef2a426d8f29082066ad228b7d39f6a5eb0654f26feb76afdffc56712377b`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 7.49, consistent with packed or encrypted content.
`objdata_01_off0001e2af.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x1E2AF	45121 bytes
SHA-256: `c8812dfa10faa060e7cf96e5f802d753d1b49f389fa2bb447354ac193a2eda36`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 7.49, consistent with packed or encrypted content.
`objdata_02_off00039c27.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x39C27	45121 bytes
SHA-256: `d46324987b707c8d2cfdaf1d877d3c71bfb25f5ab74b2628761eb05018b30c0a`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 7.49, consistent with packed or encrypted content.
`objdata_03_off0005559f.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x5559F	45121 bytes
SHA-256: `f3511e51f75bac58e7f9182f145c67188e1ebfb1feeab2844cc10dcf025f13ef`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 7.48, consistent with packed or encrypted content.

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