Malicious RTF — malware analysis report

Static analysis result for SHA-256 50df6fe20891683f…

MALICIOUS

RTF

44.4 KB Created: 2017-11-21 First seen: 2017-11-29
MD5: c924c649a30a9efe7860dc82008fc9a1 SHA-1: 021245507df6a00d026754aff835cb6ddc13189a SHA-256: 50df6fe20891683f68215385a5c9d4e53c254cf1fb0d0d259f7de6c0949a9dd2
142 Risk Score

Malware Insights

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

The RTF document contains a critical heuristic indicating exploitation of CVE-2017-0199, which is used to fetch a secondary document from the URL http://185.24.233.241/3/aap1.doc. The document also contains a lure to enable editing, suggesting it is intended to be delivered as an attachment via spearphishing.

Heuristics 5

  • 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.
  • 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.
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings
  • 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://185.24.233.241/3/aap1.doc In RTF body
    • http://schemas.microsoft.com/office/word/2003/wordmlIn RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00003376.bin rtf-objdata-decoded RTF \objdata at offset 0x3376 3640 bytes
SHA-256: 7ca340ce0324cc898461c7a3bf4f1ed63889434b34fcf01f019e727e6223d549