Malicious Office (OLE) / .XLS — malware analysis report

Static analysis result for SHA-256 2973ffb4d0e5480a…

MALICIOUS

Office (OLE) / .XLS

64.6 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: 4a16b764c20c9cbd34ad905d0e174927 SHA-1: f25df2ee2bb928046dc9a343240a6e5a6207e1e1 SHA-256: 2973ffb4d0e5480a27c6bfbc73e17f5c8826cc303ad08180b13d28dfd5afb0d6
140 Risk Score

Malware Insights

MITRE ATT&CK
T1059.003 Windows Command Shell

The sample is an Excel spreadsheet exhibiting malicious characteristics. It contains a reference to the WinExec API, indicating it likely attempts to execute a command or program. Additionally, XOR-encoded strings were detected, suggesting obfuscation of malicious content. The large slack space in the OLE structure is also anomalous and often associated with packed or obfuscated malware.

Heuristics 3

  • XOR-encoded strings (key 0x98) critical SC_XOR_ENCODED
    Found 8 Windows library/API name(s) XOR-encoded with single-byte key 0x98: 'wininet.dll', 'LoadLibraryA', 'GetProcAddress', 'CreateFileA', 'InternetOpenA', 'HttpOpenRequestA', 'HttpSendRequestA', 'RegOpenKeyExA'
  • Reference to WinExec API high SC_STR_WINEXEC
    Reference to WinExec API
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 66,186 bytes but its declared streams total only 24,565 bytes — 41,621 bytes (63%) live in unallocated sector slack. This is the canonical hiding place for pre-macro-era Office exploit payloads (XOR-encoded shellcode reached via a parser pointer-corruption bug in the document structure).

Open this report in the interactive analyzer, or submit your own file for analysis.