Malicious RTF — malware analysis report

Static analysis result for SHA-256 e2e07e0a0dd69a1e…

MALICIOUS

RTF

401.6 KB First seen: 2021-02-02
MD5: 53d0e4fe4c272f7eb9bac1c9668014eb SHA-1: 6a8e59249528594e7eeb75ec90e171d724081586 SHA-256: e2e07e0a0dd69a1e046f87635d5d4543662eb693290839874307a2753768fafc
320 Risk Score

Heuristics 8

  • 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
🗂 Part of campaign: shared payload 9898055bd0 6 samples

Related samples 8

Ranked by shared artifacts, heuristics, extracted URLs, CVEs, and signatures.

Full JSON: related samples API

Extracted artifacts 4

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000007f8.bin rtf-objdata-decoded RTF \objdata at offset 0x7F8 98624 bytes
SHA-256: 18d82e61faf1aca2fdfcd473a5f8db429e26c45df5bb121aca1095e45757da49
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): Wscript.Shell"" ) ")
objdata_01_off00004106.bin rtf-objdata-decoded RTF \objdata at offset 0x4106 98598 bytes
SHA-256: 0155531bbffa6286fc996c046a65d9d0b5d49e0f0d212a62b110ead34eb8fb66
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): Wscript.Shell"" ) ")
objdata_02_off000362c3.bin rtf-objdata-decoded RTF \objdata at offset 0x362C3 2632 bytes
SHA-256: 9898055bd0f8f4ea4768ba3581db647387d886eacf12252bf69adb6e4fce9c36
objdata_03_off00037866.bin rtf-objdata-decoded RTF \objdata at offset 0x37866 12297 bytes
SHA-256: e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7

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