Malicious RTF — malware analysis report

Static analysis result for SHA-256 dbbcd373a29e95d3…

MALICIOUS

RTF

57.3 KB First seen: 2019-04-17
MD5: a8d078f7eff1760319b025b5f8502961 SHA-1: 31945a331b98bb5fb7cc80bf6c499cbfdd6b0cb5 SHA-256: dbbcd373a29e95d3a2c82f2ba7e1b0176620c939391161f22ee9e394475e339c
142 Risk Score

Malware Insights

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

The RTF file contains embedded OLE object data and specifically triggers heuristics for the Equation Editor vulnerability. This indicates an attempt to exploit a known weakness for code execution. The presence of shellcode API strings in the extracted artifact further supports the likelihood of a secondary payload being downloaded and executed.

Heuristics 5

  • Split hex Equation Editor ProgID + OLE object critical CVE likely RTF_EQUATION_EDITOR
    RTF embeds the Equation.3 ProgID as hex bytes near OLE object activation and splits the byte stream with whitespace or an ignorable RTF group. This is an Equation Editor OLE activation surface commonly used by CVE-2017-11882 / CVE-2018-0802 exploit documents.
  • \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
  • 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.
  • 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://schemas.microsoft.com/office/word/2003/wordml In RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000dac0.bin rtf-objdata-decoded RTF \objdata at offset 0xDAC0 1316 bytes
SHA-256: d0d59838db87238a6d941334dd0d0e7dde03e571d79028be0db7e132d02dca1b
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_STR_LOADLIBRARY, SC_STR_URLDOWNLOAD, SC_PEB_ACCESS Static shellcode analysis recovered API/import strings: LoadLibraryW, GetProcAddress, URLDownloadToFileW, ExitProcess, ShellExecuteW