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

Static analysis result for SHA-256 d4606d9da642da1e…

MALICIOUS

Office (OLE) / .XLS

170.6 KB
MD5: 0018a584b021fad2c0f42ef95ad51d06 SHA-1: d4d97b32e8ee181530811725625c08c88c738ac1 SHA-256: d4606d9da642da1e9aba205f98f65094313c03220553b9c503961006f1fe8589
160 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File T1059.001 PowerShell T1105 Ingress Tool Transfer

The sample is a malicious Excel spreadsheet that exhibits characteristics of a downloader. High-severity heuristics indicate the use of Windows API functions like VirtualAlloc, VirtualProtect, LoadLibrary, and GetProcAddress, which are commonly used by malware to allocate memory and load executable code. The OLE slack anomaly suggests potential obfuscation or embedded malicious content. Although no specific URLs or scripts were extracted, the combination of API calls points towards the execution of a second-stage payload. The document body is heavily corrupted and unreadable, providing no further context.

Heuristics 6

  • 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 174,704 bytes but its declared streams total only 56,346 bytes — 118,358 bytes (68%) 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).
  • Reference to VirtualAlloc API medium SC_STR_VIRTUALALLOC
    Reference to VirtualAlloc API
  • Reference to VirtualProtect API medium SC_STR_VIRTUALPROTECT
    Reference to VirtualProtect API
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://www.microsoft.com
    • https://www.verisign.com/rpa
    • http://ocsp.verisign.com/ocsp/status0
    • https://www.verisign.com/rpa0
    • http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl0