RTF malware analysis — malicious · d875d3a0da6273c4

MALICIOUS

RTF

82.3 KB Created: 2019-01-23 19:55:00 First seen: 2019-12-10

MD5: 3988dd4f640876c65750e205488a8bd2 SHA-1: 42be2878b6986a20df816bfb60e38328b1a92717 SHA-256: d875d3a0da6273c4723b602d7d0cc09b0064ced54cbbb7ea3ae6b6a568c2922d

242 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains embedded OLE objects and triggers critical heuristics for CVE-2017-8759, indicating exploitation for client execution. The presence of extracted artifacts like 'objdata_00_off0000e087.bin' and 'objdata_01_off00013b80.bin' suggests these are components of the malicious payload. The document likely serves as a spearphishing attachment designed to exploit this vulnerability.

Heuristics 6

Split hex Equation Editor ProgID + OLE object critical CVE likely RTF_EQUATION_EDITOR

RTF embeds the Equation.3 ProgID as hex bytes near OLE object activation and splits the byte stream with whitespace or an ignorable RTF group. This is an Equation Editor OLE activation surface commonly used by CVE-2017-11882 / CVE-2018-0802 exploit documents.
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.
Suspicious extracted artifact critical 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.
\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 2 \objdata section(s) — embedded OLE objects
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
- http://bit.ly/2D9cr6bIn RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off0000e087.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xE087	3800 bytes
SHA-256: `6bd8dc3ae4ab59c28d8238532a583355b8507a772ea691fe5e10bb980d893ebe`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 long base64-like blob(s).
`objdata_01_off00013b80.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x13B80	1403 bytes
SHA-256: `47e5af7af72ecce1613e0e095aa268867cedfe26b081ebbda043432b73eb6426`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered URL(s): http://bit.ly/2D9cr6b Static shellcode analysis found candidate code region(s). Indicators: SC_STR_LOADLIBRARY, SC_STR_URLDOWNLOAD, SC_PEB_ACCESS Static shellcode analysis recovered API/import strings: LoadLibraryA, GetProcAddress, URLDownloadToFileA, ShellExecuteA, ExitProcess

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