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

Static analysis result for SHA-256 544920c2649d9eae…

MALICIOUS

Office (OLE) / .XLS

117.0 KB Created: 1996-12-17 01:32:42 Authoring application: Microsoft Excel
MD5: fde354e2f19d63b082ba807c2c17ec52 SHA-1: d73fe5cffe829e7a0105acc93c395d47a2770a9b SHA-256: 544920c2649d9eae11a8da3131ee97fe133512ffc205a777209eb7dc5e11a5cb
160 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File

The sample is an OLE Excel document with a significant amount of slack space, indicating potential obfuscation or embedded malicious content. Heuristics indicate the use of Windows API functions CreateProcess, LoadLibrary, and GetProcAddress, strongly suggesting the execution of arbitrary code. The document body is minimal, providing no further context for the attack pattern.

Heuristics 4

  • Reference to CreateProcess API high SC_STR_CREATEPROCESS
    Reference to CreateProcess API
  • Reference to LoadLibrary API high SC_STR_LOADLIBRARY
    Reference to LoadLibrary API
  • Reference to GetProcAddress API high SC_STR_GETPROCADDRESS
    Reference to GetProcAddress API
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 119,808 bytes but its declared streams total only 24,565 bytes — 95,243 bytes (79%) 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).