Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 5ce7c16e29937c5f…

MALICIOUS

Office (OLE)

52.5 KB Created: 2013-02-05 10:04:55 Authoring application: Microsoft Excel First seen: 2015-04-05
MD5: b3f3ee5252d3abe2e7474f55f71071b3 SHA-1: 73b38363262d032c5d6e8fff0a7840dfcd22f407 SHA-256: 5ce7c16e29937c5f90ffc48d5e0affae5b3dd523be71fdbe5a321fd91c6fbc69
140 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1105 Ingress Tool Transfer

The sample is an Excel file that uses a social engineering lure, claiming a newer version of Microsoft Office is required to view content, prompting the user to enable macros. The critical heuristic indicates an OLE package that drops an auto-executable payload named 'http185.39.149.119zxrssidin.exe.vbs', suggesting it downloads and executes a second-stage malware. The reference to Windows Script Host further supports the execution of a script.

Heuristics 3

  • 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: MBD033319BD/Ole10Native 9757 bytes
SHA-256: e9b464cb938354929b72785cc45d45d568406147679dda8e2f525064ed54c614
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): WScript.Shell").Run(""& iflhaayAnnAAnuqyb &""),0A