Malicious RTF — malware analysis report

Static analysis result for SHA-256 96ed7bbea05bb5fb…

MALICIOUS

RTF

40.5 KB Created: 2017-11-17 16:12:00 First seen: 2017-11-20
MD5: e53e8de199492089f4f8949a69f24165 SHA-1: e74e7e838635d725b69f39c9fb594e408e3927ba SHA-256: 96ed7bbea05bb5fb2059c06162102c1a4175be9c8a40a0ed8c5d0bc54a8b7371
142 Risk Score

Malware Insights

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

The RTF document contains an OLE object that exploits CVE-2017-0199, a known vulnerability for remote code execution. The embedded object attempts to download a secondary document from the URL http://185.242.233.241/0/1jud.doc. The document also contains a lure to enable editing, indicating it is designed to bypass security measures and execute its payload.

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/0/1jud.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_off00003426.bin rtf-objdata-decoded RTF \objdata at offset 0x3426 3640 bytes
SHA-256: 4208afbab2f21445a3f6143cbcc8035dc92c08b57ca7bd604deb6218d4ded7cf