Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 244126a2873c26f7…

MALICIOUS

Office (OLE)

50.0 KB Created: 2013-02-05 10:04:55 Authoring application: Microsoft Excel First seen: 2015-04-05
MD5: 8e693d82c11779cf21c3e2e847e8e1af SHA-1: e0a4f11511374326fdaca2778845e4269aadf006 SHA-256: 244126a2873c26f76d9dfa8f993b4209ac8a52fd00a91d98a23c0c90764d1a73
200 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The file is an Excel document that uses a social engineering lure to convince the user to enable content, likely to execute a malicious payload. Heuristics indicate that the document package drops an executable file named 'http193.26.217.221zxrssidin.exe.vbs', which is likely a VBScript downloader. The presence of 'SC_STR_WSCRIPT' heuristic further supports the execution of a script via Windows Script Host.

Heuristics 4

  • ClamAV: Xls.Dropper.Agent-1822175 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Xls.Dropper.Agent-1822175
  • Ole10Native package drops an auto-executable payload critical OFFICE_PACKAGE_RISKY_FILE
    OLE Package displayName or fullPath ends in a directly auto-executable extension (a runnable binary or a script the default shell host runs on double-click). Embedding such a payload inside an Office document has no benign authoring use — it is a malware-delivery dropper.
  • Reference to Windows Script Host high SC_STR_WSCRIPT
    Reference to Windows Script Host
  • Suspicious extracted artifact high 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
ole10native_00.bin ole-package OLE Ole10Native stream: MBD0333159D/Ole10Native 7369 bytes
SHA-256: a77aa73a58e3489ad143582b6aeaac8ae9846fc102e3d03802aff9ba0be6d193
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): WScript.Shell").Run(""& cizucdvwxalyuljcs &""),0>