Malicious RTF — malware analysis report

Static analysis result for SHA-256 a3153224248fe4e3…

MALICIOUS

RTF

1.22 MB First seen: 2019-03-10
MD5: a293af1b6f5a3c2b7ce97183259d73c0 SHA-1: cc27f2583443b48e0fa0a06fc6f26914cf27f696 SHA-256: a3153224248fe4e3988c386090c9198922df31e3469e0ceb7d5999faf1711886
242 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains multiple indicators of exploitation for CVE-2017-8570, including the presence of Composite Monikers and OLE object data. This vulnerability is known to be used for dropping and executing script files, likely to download and run a second-stage payload. The excessive hex data within the OLE object further suggests the presence of a hidden 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.
  • \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.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~1162KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 7 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • Suspicious extracted artifact medium 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://schemas.openxmlformats.org/drawingml/2006/main In RTF body
    • http://schemas.microsoft.com/sharepoint/v3/contenttype/formsIn RTF body
    • http://schemas.openxmlformats.org/officeDocument/2006/customXmlIn RTF body

Extracted artifacts 7

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000025.bin rtf-objdata-decoded RTF \objdata at offset 0x25 205 bytes
SHA-256: 75a725fc96463ea024899f12597b26031b1a5d84ddd2de407d47914073b3db59
objdata_01_off000001ea.bin rtf-objdata-decoded RTF \objdata at offset 0x1EA 479435 bytes
SHA-256: 4066894364ff5f5b7d97cd09ebce2141a7c457285f0eeef2656876384d6302b4
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL, SC_GETPC_CALL
objdata_02_off0011c048.bin rtf-objdata-decoded RTF \objdata at offset 0x11C048 1068 bytes
SHA-256: 2b28d78ceb2a564ae30f2b6865926b068f3f920a373c2e3fc4cb865091eddd89
objdata_03_off0011c8d3.bin rtf-objdata-decoded RTF \objdata at offset 0x11C8D3 51404 bytes
SHA-256: f1610a5bc8dc649cc9ab31720cfc79b8997d59aed4c8547e159ef92d1223ca13
objdata_04_off00135a9d.bin rtf-objdata-decoded RTF \objdata at offset 0x135A9D 369 bytes
SHA-256: 3c0b4878e98d51d984a06b9ba36e54869ecd67e41f335730fced4ca28976d877
objdata_05_off00135db3.bin rtf-objdata-decoded RTF \objdata at offset 0x135DB3 890 bytes
SHA-256: 21dcdf875b1972c61c0e8c2c2123f9a95c8f29fb4a2cf8bf52511b328881de8e
objdata_06_off0013650e.bin rtf-objdata-decoded RTF \objdata at offset 0x13650E 2633 bytes
SHA-256: 27c6d10cfe7974ebf40c1200cc005f9878cc37b7d49ece9cbc396d700c38918a

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