Malicious RTF — malware analysis report

Static analysis result for SHA-256 a2586041227c89eb…

MALICIOUS

RTF

338.6 KB Authoring application: Riched20 10.0.17134 First seen: 2021-02-09
MD5: e484b996bec6cc25676fe02d19425d08 SHA-1: 3b190fa3c0b0e350b6b2fbca34043994ba22d1e3 SHA-256: a2586041227c89ebf09b41f5d81f32f5e04659440c833916b92d1bccc86f9e4a
260 Risk Score

Heuristics 6

  • 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.
  • ClamAV: Xls.Malware.Sload-7135989-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Xls.Malware.Sload-7135989-0
  • \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 5 \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.

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000113.bin rtf-objdata-decoded RTF \objdata at offset 0x113 33696 bytes
SHA-256: 5f97e71d6765a415ee1b242db379598174f8a2d1704aebef3e1416018ae2ed77
Detection
ClamAV: Xls.Malware.Sload-7135989-0
Obfuscation or payload: unlikely
objdata_01_off00010fcc.bin rtf-objdata-decoded RTF \objdata at offset 0x10FCC 33696 bytes
SHA-256: 8a9f9e33e999d5df22864d3978e212b467f2df4e75fdcb6efba80ed8e19a18cd
Detection
ClamAV: Xls.Malware.Sload-7135989-0
Obfuscation or payload: unlikely

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