Malicious RTF — malware analysis report

Static analysis result for SHA-256 5f50f37716f6fb25…

MALICIOUS

RTF

508.1 KB First seen: 2019-01-25
MD5: e2a4ab5ae1aae660e9277adb47994e8e SHA-1: d161d169e9b4a5602024aafd776492c790f01e8e SHA-256: 5f50f37716f6fb258f54b8486186afa189641be4e714e10e0fe0ca73fc82e2a0
344 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains multiple indicators of malicious activity, including OLE object data, a composite moniker, and a PE header within hex data. Crucially, it exploits CVE-2017-8570, which is known to drop a script file. An extracted artifact, objdata_05_off00006688.bin, is also flagged as suspicious and likely contains the second-stage payload.

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.
  • 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: Win.Trojan.0053d-7077246-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Trojan.0053d-7077246-0
  • PE header (with DOS stub) in hex data critical RTF_MZ_HEX
    Hex-encoded PE (MZ + DOS stub) found inside RTF — likely an embedded executable payload
  • \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 6 \objdata section(s) — embedded OLE objects
  • Suspicious extracted artifact info 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://nsis.sf.net/NSIS_Error In RTF body

Extracted artifacts 6

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000002f.bin rtf-objdata-decoded RTF \objdata at offset 0x2F 873 bytes
SHA-256: c481ae32e55cd5aed2c08c2e2d44fffd4c3c894b98dd0aadef7fe1bcc1714b99
objdata_01_off00004204.bin rtf-objdata-decoded RTF \objdata at offset 0x4204 612 bytes
SHA-256: c62851521e10316dfd43f2b6ee67cc27e2a24456bb346c8fa9dc4a6d6e21d526
objdata_02_off00004704.bin rtf-objdata-decoded RTF \objdata at offset 0x4704 487 bytes
SHA-256: fbdc08917d7c4e786f601c1fc37cd61fc0fa1fdd4c6590c37bf66bf37ded9f73
objdata_03_off00004b0e.bin rtf-objdata-decoded RTF \objdata at offset 0x4B0E 833 bytes
SHA-256: a57103bc84a2998af640e20eec949b44c7cbeb12765e1e7ce6b5161436b0b531
objdata_04_off00005201.bin rtf-objdata-decoded RTF \objdata at offset 0x5201 2633 bytes
SHA-256: 1feb5f150bb35566d1a01fc59a357dc0ea34bc7498e0ec99bd939f6f848044b0
objdata_05_off000066e1.bin rtf-objdata-decoded RTF \objdata at offset 0x66E1 246961 bytes
SHA-256: bc7ca05cb227e9ff0a87b456a809ad7abf64c9e1915d3f5abb79ea2ce94de659
Detection
ClamAV: Win.Trojan.0053d-7077246-0
Obfuscation or payload: likely
Carved artifact entropy is 7.92, consistent with packed or encrypted content.