Malicious RTF — malware analysis report

Static analysis result for SHA-256 db2f10bf28a98105…

MALICIOUS

RTF

654.9 KB First seen: 2021-04-01
MD5: b7e505eeed8ceaebf00895ac68ad610c SHA-1: be959aaf7ce34d4bc4c5eb9e44795a0319ab92b4 SHA-256: db2f10bf28a981051e22308cc53bcfd0dc5ab2ebf4e3fc31a70737a218cbe7c0
340 Risk Score

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.
  • CVE-2017-0199 / CVE-2017-8759 (OLE2Link auto-activated remote loader) critical CVE related RTF_OLE2LINK_REMOTE_MONIKER_LOADER
    RTF embeds an OLE2Link object that is force-activated with \objupdate (no user interaction on open) and fetches a remote second stage — through an INCLUDETEXT/INCLUDEPICTURE field or the OLE object's own moniker. This is the OLE2Link auto-update attack path shared by CVE-2017-0199 (server returns an HTA/scriptlet) and CVE-2017-8759 (server returns a SOAP WSDL the .NET parser compiles). Office processes the fetched response through the same code path; the specific CVE depends on the now-unreachable server content type.
  • 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
  • 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 4

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000983.bin rtf-objdata-decoded RTF \objdata at offset 0x983 217434 bytes
SHA-256: 4c42eb5691c126221fedcd42e9445f49ae2aac1edb14ee110652e55b4d319e65
objdata_01_off00007132.bin rtf-objdata-decoded RTF \objdata at offset 0x7132 217407 bytes
SHA-256: 515bef027447c6112c7bae044a18152734264117ee7fb75c7a19398369045be3
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): WScript.Shell"")")
objdata_02_off00075841.bin rtf-objdata-decoded RTF \objdata at offset 0x75841 2632 bytes
SHA-256: 3cd3b7d42e5855c90d6d11c54ef2670ed8970441480cc23f7d39ef08fa1c935b
objdata_03_off00076de4.bin rtf-objdata-decoded RTF \objdata at offset 0x76DE4 12297 bytes
SHA-256: e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7