Malicious RTF — malware analysis report

Static analysis result for SHA-256 a9a71db16c14dd14…

MALICIOUS

RTF

8.3 KB First seen: 2019-11-20
MD5: 468c9e591ed36b73c861dec8ac2ec7d1 SHA-1: 16282903ab9313a411b5eb854c567e34d2c42461 SHA-256: a9a71db16c14dd14dca63faa7a2f3fd4312ea215df97510fdfdd9f31248781b9
160 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object, specifically triggering the Equation Editor vulnerability. This technique is commonly used to achieve arbitrary code execution. The presence of shellcode candidate regions within the extracted OLE object data further supports this. The file is likely a spearphishing attachment designed to exploit this vulnerability to download and execute a secondary payload.

Heuristics 5

  • Equation Editor CLSID critical CVE likely RTF_EQUATION_EDITOR
    Equation Editor OLE CLSID found inside an OLE object — exploited by CVE-2017-11882 / CVE-2018-0802 / CVE-2018-0798
  • \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 OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • Suspicious extracted artifact medium EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000032.bin rtf-objdata-decoded RTF \objdata at offset 0x32 4148 bytes
SHA-256: 53e66af5c992883dcfac59acd12942591c4a7db95f29b5341bbac908fd0fddac
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL