Malicious RTF — malware analysis report

Static analysis result for SHA-256 8511a7d115e04255…

MALICIOUS

RTF

3.16 MB First seen: 2022-07-26
MD5: 3ef8531e16fb08f496c9c1088523890b SHA-1: aa5d6576b7a96bc48ed9aaf4778a61de788f4209 SHA-256: 8511a7d115e04255a72a2b87b35f3c4ebc1d53bcd8352734f4bfd833b4e544b9
442 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File T1559.001 Component Object Model Hijacking

The RTF file contains multiple indicators of exploitation, including RTF_EQUATION_EDITOR, CVE_2017_11882_ACTIVATION_RELATED, and RTF_MZ_HEX, strongly suggesting the use of the Equation Editor vulnerability. ClamAV detections for Rtf.Dropper.Agent-9965975-1 and Win.Trojan.AsyncRAT-9914220-0 on an extracted artifact indicate the file acts as a dropper for a trojan. The presence of large, hex-encoded OLE objects further supports the payload delivery mechanism.

Heuristics 11

  • Equation Editor activation — CVE-2017-11882 related high CVE related CVE_2017_11882_ACTIVATION_RELATED
    RTF decodes to an Equation.3 ProgID and requests OLE activation with \objemb plus \objupdate. This reaches the legacy Equation Editor attack surface used by CVE-2017-11882/CVE-2018-0802 documents, but the malformed MTEF/native payload needed for stronger attribution was not recovered.
  • Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED
    RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
  • Split hex Equation Editor ProgID + OLE object critical 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.
  • PE header (with DOS stub) in hex data critical RTF_MZ_HEX
    Hex-encoded PE (MZ + DOS stub) found inside RTF — likely an embedded executable payload
  • ClamAV: Rtf.Dropper.Agent-9965975-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Rtf.Dropper.Agent-9965975-1
  • ClamAV detection on extracted artifact critical EXTRACTED_FILE_CLAMAV
    ClamAV flagged at least one file extracted from inside this sample. Even when the wrapping document carries no AV detection of its own, a hit on the carved artifact is a strong indicator the sample is a delivery vehicle.
  • \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.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~1762KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • Suspicious extracted artifact info 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 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001284.bin
8128d5e7511389a557aba820a612016cc1b15e2b32714241aea1ca1685604af2
rtf-objdata-decoded RTF \objdata at offset 0x1284 898859 bytes
Detection
ClamAV: Win.Trojan.AsyncRAT-9914220-0
Obfuscation or payload: likely
Carved artifact entropy is 7.94, consistent with packed or encrypted content.
objdata_01_off001c3a22.bin
a9ff9a80fcbe35345bbc4e4eca2212ef4c041b9f9a7826aafeaaa45782edf0a1
rtf-objdata-decoded RTF \objdata at offset 0x1C3A22 346904 bytes