RTF malware analysis — malicious · caaf44f16dcbee93

MALICIOUS

RTF

79.4 KB Created: 2021-05-19 03:24:00 First seen: 2021-05-29

MD5: 344b7370c6e61812eeb1cf1d737f27f3 SHA-1: 64499252233f47ba779fa66e852be97a359ede2c SHA-256: caaf44f16dcbee93071887ab6844ed79975ccd20f9008deb93c13bfdb436e0b0

262 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple indicators of exploitation for known vulnerabilities, specifically CVE-2017-11882 (Equation Editor) and CVE-2017-8759 (MSXML SAX OLE activation). These vulnerabilities are often leveraged to embed and execute malicious OLE objects. The presence of extracted files and the RTF_OBJUPDATE heuristic suggest an attempt to force OLE activation, likely to download and execute a secondary payload. The document body itself is a lure related to port resilience training, masking the malicious intent.

Heuristics 8

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.
Equation Editor activation — CVE-2017-11882 related high CVE related CVE_2017_11882_ACTIVATION_RELATED

RTF decodes to an Equation.3 ProgID and requests OLE activation with \objemb plus \objupdate. This reaches the legacy Equation Editor attack surface used by CVE-2017-11882/CVE-2018-0802 documents, but the malformed MTEF/native payload needed for stronger attribution was not recovered.
\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 3 \objdata section(s) — embedded OLE objects
Embedded OLE object medium RTF_OBJEMB

RTF contains \objemb — embedded OLE object
Suspicious extracted artifact medium 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://www.pmaesa.org/wp-content/uploads/2021/05/BPR_Course-Details_June-July-2021.pdf In RTF body
- https://tft.unctad.org/ports-covid-19/In RTF body
- https://tft.unctad.org/port-management/building-port-resilience/In RTF body

Extracted artifacts 3

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off000097b5.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x97B5	19474 bytes
SHA-256: `c1f42de5d02dd1a4e6553165c91a34004b03d5d46b59c23bc41b519a33f4a58d`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis found candidate code region(s). Indicators: heap spray 0x41 (A) Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off00013001.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x13001	1709 bytes
SHA-256: `6ef048de06e9c2e6b420e78a489e52123766b08549a074a5f95b98ffe8558f38`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis found candidate code region(s). Indicators: SC_PEB_ACCESS
`objdata_02_off00013011.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x13011	36 bytes
SHA-256: `8935eb605040753f89379b3f05c2cdaefba833ec64299ed9c258020f4c1217b0`

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