Malicious RTF — malware analysis report

Static analysis result for SHA-256 20b075c5400b67a2…

MALICIOUS

RTF

4.71 MB Created: 2021-07-11 23:14:00 First seen: 2021-09-13
MD5: 1c1cb49d0e47543acfd6ec0b0aaaffaa SHA-1: b3a7b46d7601c7cb27bcba090dc8f89779605eb8 SHA-256: 20b075c5400b67a25a4a3c17e5e7adb79fb3d2753fddaf034a4f3ad27f6ea137
242 Risk Score

Malware Insights

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

The RTF file contains multiple high-severity heuristics indicating embedded OLE objects with large amounts of hex-encoded data, including a PE header. This strongly suggests the file is a dropper intended to extract and execute a secondary payload. The embedded artifact objdata_00_off002931ea.bin is likely this payload.

Heuristics 8

  • 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.
  • 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
  • Package object class high RTF_OBJCLASS_PACKAGE
    OLE Package object — can wrap arbitrary files
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~2617KB of hex-encoded data inside \objdata sections — may hide a payload
  • 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.
  • 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_off002931ea.bin rtf-objdata-decoded RTF \objdata at offset 0x2931EA 292940 bytes
SHA-256: f5a94da653091c3e33ffad4d1851b0a8bdce7cdfdb32ed4d1849939de3dacf55
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_PEB_ACCESS_X64, SC_STR_SHELLEXEC, SC_STR_GETPROCADDRESS Static shellcode analysis recovered API/import strings: advapi32.dll, shell32.dll, ADVAPI32.DLL, NtAllocateVirtualMemory, NtProtectVirtualMemory, ShellExecuteA