Malicious RTF — malware analysis report

Static analysis result for SHA-256 861516904f13a216…

MALICIOUS

RTF

236.5 KB Created: 2012-04-19 15:10:00 Authoring application: Microsoft Word 11.0.0000 First seen: 2015-10-13
MD5: e94f9b67a66ffaf62fb5ce87b677dc5c SHA-1: a7b902f6bc0777b4ee59b342ecfe9b3cdf54db54 SHA-256: 861516904f13a21648d0f00d28885134d60d98dcc0f6a6e02cf2fcf50f92e7e0
82 Risk Score

Heuristics 4

  • 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 5 \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_off000013c5.bin rtf-objdata-decoded RTF \objdata at offset 0x13C5 39957 bytes
SHA-256: 05fa1808a93acba7ac1c4ffd3dd0905d90e138119a6ae0fbb42e645009815d65
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_PEB_ACCESS