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

Static analysis result for SHA-256 86391280bbab8896…

MALICIOUS

Office (OLE) / .XLS

192.5 KB Created: 1996-10-14 23:33:28 Authoring application: Microsoft Excel
MD5: cfb72fdb58b113c38119d4e941ec1ea5 SHA-1: 3d593e3866fe546b1e75e90cdeea6da9aac5c3fd SHA-256: 86391280bbab889650f1f39c2e953d12c3b0282dcf4f4808a6cc1450dd6c173b
180 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The file is an OLE document exhibiting characteristics of an appended payload and large slack space, indicative of a packed or obfuscated executable. The presence of heuristics related to CVE-2009-0556 suggests an attempt to exploit a client-side vulnerability for execution. The XOR-encoded strings further support the obfuscation of malicious content within the document.

Heuristics 4

  • PowerPoint OffArray-style record stub — CVE-2009-0556 related high CVE related PPT_CVE_2009_0556_RELATED
    Small embedded PowerPoint Document stream contains the sparse record set associated with OffArray-style exploit stubs and lacks normal text/placeholder atoms. This is CVE-2009-0556-family evidence, reported as related until the malformed OffArray field is validated directly.
  • XOR-encoded strings (key 0xFC) critical SC_XOR_ENCODED
    Found 5 Windows library/API name(s) XOR-encoded with single-byte key 0xFC: 'LoadLibraryA', 'GetProcAddress', 'VirtualAlloc', 'CreateProcessA', 'RegOpenKeyExA'
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 197,120 bytes but its declared streams total only 15,628 bytes — 181,492 bytes (92%) 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).
  • OLE file has appended executable-looking payload bytes high OLE_APPENDED_PAYLOAD
    OLE compound file contains a large high-entropy region beyond the declared major streams and that region includes shellcode, PE, or loader API markers. This is a payload-carrier signal, not a specific CVE attribution by itself.

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