Malicious RTF — malware analysis report

Static analysis result for SHA-256 b72bddf1b3ddfe92…

MALICIOUS

RTF

241.9 KB First seen: 2020-08-25
MD5: 0dd495a7d1c5863c7ef1061ab951104a SHA-1: 98daf2745c58392a17152a365c7c01a66adee8ed SHA-256: b72bddf1b3ddfe921932589e2522993f6fe38942845ded0ed0d657c6f5bd6003
300 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF file contains multiple indicators of OLE object manipulation, including composite monikers and automatic linking, strongly suggesting exploitation of CVE-2017-8570. The document body explicitly prompts the user to 'Enable Editing', a common lure for macro-based or OLE-based malware delivery. The heuristic 'CVE_2017_8570: Composite Moniker' indicates the file is designed to drop an SCT script, which is then likely executed.

Heuristics 9

  • Composite Moniker — CVE-2017-8570 (drops SCT script) critical CVE related CVE_2017_8570
    RTF \objdata decodes to OLE data containing the Composite Moniker — CVE-2017-8570 (drops SCT script) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
  • Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED
    RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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.
  • Suspicious extracted artifact high 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.
  • 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
  • OlePres presentation stream in RTF OLE object medium RTF_OLEPRES_STREAM
    RTF contains an embedded OLE object with an OlePres presentation stream. OlePres is an OLE presentation marker and is not enough on its own to identify CVE-2025-21298.
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings

Extracted artifacts 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000bc6.bin rtf-objdata-decoded RTF \objdata at offset 0xBC6 27687 bytes
SHA-256: 6cee20e83ad0caae464140f72f6ba44983f0361e6ae494eb281d2e616cb8bc10
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): Wscript.Shell"" ) ") Carved artifact contains 2 shell/COM execution token(s).
objdata_01_off0000e519.bin rtf-objdata-decoded RTF \objdata at offset 0xE519 12261 bytes
SHA-256: cfdf79b95584afe599f8bd01e391d8904839d9495e407a353433d3f5e3be3602
objdata_02_off00014529.bin rtf-objdata-decoded RTF \objdata at offset 0x14529 2632 bytes
SHA-256: 640df70a90931ea171b9bd39906ee065f8b6bb3d8f5d187057c6aa8339897ca6