Malicious RTF — malware analysis report

Static analysis result for SHA-256 658848a1d89ca697…

MALICIOUS

RTF

1.63 MB Created: 2020-07-30 02:44:00 First seen: 2020-09-07
MD5: 1bfb05aaeb6aac3a2a75b19ab5c417e6 SHA-1: cc85fc502fcd30efd8928b098f27a2ef5f95dfe7 SHA-256: 658848a1d89ca69737e6eaccb6fb9ad553761cad665dd5b2e419b55dfdb084fc
262 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 (MSXML SAX OLE activation) and CVE-2026-21514 (Word/OLE security bypass). These vulnerabilities are commonly exploited to execute arbitrary code, often to download and run further malicious content. The presence of shellcode API strings in a statically extracted artifact further supports this. The document body content appears to be a financial report, likely a lure.

Heuristics 8

  • 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 ProgID + OLE object high CVE related RTF_EQUATION_EDITOR
    RTF references Equation.3 ProgID alongside \objdata — likely Equation Editor (CVE-2017-11882 / CVE-2018-0802 / CVE-2018-0798) but without the binary CLSID payload, so flagged at HIGH instead of CRITICAL.
  • CVE-2026-21514 — Word/OLE security bypass in RTF high CVE likely CVE_2026_21514
    RTF contains a hidden \svb hex package with DrsE2oDoc and downRevStg drawing compatibility parts. This matches an observed CVE-2026-21514 exploitation shape that manipulates Word's internal document structure and trust decisions.
  • Equation Editor object class critical RTF_OBJCLASS_EQUATION
    Object class 'equation.3' references Equation Editor
  • 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
  • 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://schemas.m In RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0018ca37.bin rtf-objdata-decoded RTF \objdata at offset 0x18CA37 14250 bytes
SHA-256: 6cf3db9ff941b26f561c84ca4a2f9de498ff2a1e0e4b2c7dc127e62aed0d69a6
Detection
ClamAV: No threats found
Obfuscation or payload: likely
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: LoadLibraryW, GetProcAddress, URLDownloadToFileW, ExitProcess
rtf_svb_0000e031.zip rtf-svb-package RTF \svb hex-decoded ZIP at offset 0xE031 1995 bytes
SHA-256: 4861c2bad0eca8ebfd9f6c7d96bffb59367aa1a49ae3381f1bd38a7414945026

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