Malicious RTF — malware analysis report

Static analysis result for SHA-256 d34ac4fc46547f00…

MALICIOUS

RTF

5.6 KB Authoring application: Msftedit 5.41.21.2510 First seen: 2019-03-10
MD5: c94c774e5dcb0ababe23d228d3ba4509 SHA-1: 1258f30995b2d6c33884460435a3edf15bfd2def SHA-256: d34ac4fc46547f0038e0d98b962a541ea19ef2c93dca6159fbfa5f6ac4aee705
222 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains an OLE object that is automatically linked and updated, triggering CVE-2017-0199. This exploit is designed to download and execute a secondary payload from the embedded URL http://test.lr3800.com/exploit.html. The ClamAV detection further confirms the malicious nature of the file, specifically identifying it as an exploit targeting CVE-2017-0199.

Heuristics 6

  • CVE-2017-0199 (OLE2Link / remote URL Moniker) critical CVE likely CVE_2017_0199
    RTF contains a URL Moniker OLE link whose decoded target is remote. Office can fetch and process the response through the CVE-2017-0199 OLE2Link attack path, but the server-side content type is not proven statically.
  • ClamAV: Rtf.Exploit.CVE_2017_0199-6335035-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Rtf.Exploit.CVE_2017_0199-6335035-0
  • 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.
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects
  • 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://test.lr3800.com/exploit.html In RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000105.bin rtf-objdata-decoded RTF \objdata at offset 0x105 2724 bytes
SHA-256: 0ebf7341efe59ad0db0b6ebcf751e31c1f2103f813cc6e50bfe54eab2e7e188e