Malicious RTF — malware analysis report

Static analysis result for SHA-256 63613b9bec0c2f2c…

MALICIOUS

RTF

17.2 KB First seen: 2021-04-01
MD5: c3e007dd7880cae914eee2669ca7fc85 SHA-1: 242eef1d4f97eb97b26d76f12660f2274d58ee81 SHA-256: 63613b9bec0c2f2c15d751eadb974d88e63f1b2599d2da0ad6ddb240f3fb8b38
102 Risk Score

Heuristics 5

  • MSCOMCTL.ListView — CVE-2012-0158 high CVE related CVE_2012_0158
    RTF \objdata decodes to OLE data containing the MSCOMCTL.ListView — CVE-2012-0158 CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings
  • 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://94.102.63.7/putty.exe In RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000cf1.bin rtf-objdata-decoded RTF \objdata at offset 0xCF1 5700 bytes
SHA-256: 1bbe2f007a5d4ff56cdc382a0492beee80dbe9cd4651c683af7eb8a30c7131b0
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_PEB_ACCESS