Malicious RTF — malware analysis report

Static analysis result for SHA-256 d94f36f313d2f871…

MALICIOUS

RTF

2.02 MB First seen: 2019-01-11
MD5: fd95eb354383a184cd32a63b10514442 SHA-1: 09d5bc66a0b5e0c1d33ccf7846a85e49d2c70f0a SHA-256: d94f36f313d2f87178ec8139dc069c08e7d69be79f3f3caa6b9df3c45a6fa7e7
222 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains multiple indicators of malicious activity, including the critical CVE-2017-8570 heuristic which suggests the exploitation of a vulnerability to drop a script. The presence of OLE object data and excessive hex data further supports the likelihood of a hidden payload. The file likely attempts to execute a second-stage payload via the exploited vulnerability.

Heuristics 7

  • 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 ~1938KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 9 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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.microsoft.com/office/word/2003/wordml In RTF body

Extracted artifacts 8

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: 980870ba17beb12f03c3941a0cfa655d820816cec9104090156a6ea6ece5ce8a
objdata_01_off000001ee.bin rtf-objdata-decoded RTF \objdata at offset 0x1EE 969099 bytes
SHA-256: 0559e6ade9a840882c6939ece1a84c4b794a5dcbd52738e6339248a4d4552055
objdata_02_off001f1b6b.bin rtf-objdata-decoded RTF \objdata at offset 0x1F1B6B 1004 bytes
SHA-256: de57d2083ef5e021ec705be7e3dd4b0e90d1d2f7950e0bc7ffde2709f639f965
objdata_03_off001f237c.bin rtf-objdata-decoded RTF \objdata at offset 0x1F237C 31676 bytes
SHA-256: 8e1be3feb782a829ff258a0e054e4c260ab6864e307e975e6874709ef91bf7cf
objdata_04_off00201b2c.bin rtf-objdata-decoded RTF \objdata at offset 0x201B2C 359 bytes
SHA-256: 357be353baa88dc3743707bade3b7e68e8e017f02553817dd77495fda9a64957
objdata_05_off00201e36.bin rtf-objdata-decoded RTF \objdata at offset 0x201E36 866 bytes
SHA-256: 5d0695c0b0c9feed62b1faa3e75242a3007ac483afd76a69c04e9ed6b9541365
objdata_06_off00202578.bin rtf-objdata-decoded RTF \objdata at offset 0x202578 2633 bytes
SHA-256: fe11c27d916ab897eb94064e9631d8a29c847a6db39259bef31578da8d19fdf5
objdata_07_off00203a90.bin rtf-objdata-decoded RTF \objdata at offset 0x203A90 2601 bytes
SHA-256: 67ff079a9b0f053ca2843811d9da7a8fdedc7d9d377ef39d09dde148b9657c7f

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