Malicious RTF — malware analysis report

Static analysis result for SHA-256 08c4d84bc5801bbf…

MALICIOUS

RTF

3.3 KB First seen: 2020-05-25
MD5: a40b4f9c1917264d8f25d02f1da8449d SHA-1: fec3e95194516ceddbcb43de4fa1c80c89b22071 SHA-256: 08c4d84bc5801bbfe7686de03aae6dc5335c3234c0fc3007d9904dd19b5cef26
80 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 an \objupdate directive, indicating an attempt to exploit a vulnerability for client execution. The presence of shellcode candidate data further supports this. The document body is nonsensical, suggesting it is not intended for user interaction but rather to trigger the exploit.

Heuristics 3

  • \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.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000095.bin rtf-objdata-decoded RTF \objdata at offset 0x95 1322 bytes
SHA-256: 5fab1a526e7ad233aab1709097517cb400d31a5e534b3c4c884fc04aba7a171f
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL