Malicious RTF — malware analysis report

Static analysis result for SHA-256 afabd6c923ff2fd8…

MALICIOUS

RTF

2.78 MB First seen: 2019-11-20
MD5: 9018128fd2aa95d08b7c3a7945727b4c SHA-1: 7963154e2fbcce824b57f524a8561d79f9d10271 SHA-256: afabd6c923ff2fd84f06da96a4df0a581a4cb912224ba2db4e62302d3fce810e
222 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains multiple OLE objects, with one specifically identified as exploiting CVE-2017-8570 via a composite moniker. This technique is known to drop and execute a script, likely from the embedded objdata. The embedded URL 'http://test1.ru/newbuild/t.php?act=hit' is suspicious and likely serves as a download or command and control endpoint for the dropped script.

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 ~2727KB 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
  • 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://test1.ru/newbuild/t.php?act=hit In RTF body
    • http://schemas.microsoft.com/office/word/2003/wordml}}\paperw11906\paperh16838\margl1701\margr850\margt1134\margb1134\gutter0\ltrsectIn 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 1363659 bytes
SHA-256: b454e902b5dd525357a62521ef53e6fa7fd2d96b514b5bc2526a48172e60b079
objdata_02_off002b25e0.bin rtf-objdata-decoded RTF \objdata at offset 0x2B25E0 1068 bytes
SHA-256: 2b28d78ceb2a564ae30f2b6865926b068f3f920a373c2e3fc4cb865091eddd89
objdata_03_off002b2e6b.bin rtf-objdata-decoded RTF \objdata at offset 0x2B2E6B 36440 bytes
SHA-256: 11290e69c3c7b88f22214230479dc467fca6f42052bbffde39374a45d783de7d
objdata_04_off002c4b4d.bin rtf-objdata-decoded RTF \objdata at offset 0x2C4B4D 369 bytes
SHA-256: 3c0b4878e98d51d984a06b9ba36e54869ecd67e41f335730fced4ca28976d877
objdata_05_off002c4e63.bin rtf-objdata-decoded RTF \objdata at offset 0x2C4E63 890 bytes
SHA-256: 21dcdf875b1972c61c0e8c2c2123f9a95c8f29fb4a2cf8bf52511b328881de8e
objdata_06_off002c55be.bin rtf-objdata-decoded RTF \objdata at offset 0x2C55BE 2633 bytes
SHA-256: 27c6d10cfe7974ebf40c1200cc005f9878cc37b7d49ece9cbc396d700c38918a

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