Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 a1d596ef5d872eb3…

MALICIOUS

Office (OLE)

301.4 KB
MD5: b6de25e698182a651b3fc04b9ce28267 SHA-1: a51ac7ccb0496849bbb21d7f0f3a7edb75e96680 SHA-256: a1d596ef5d872eb3621423d285999822d6a7fb977f58e3c261e03d1c62f6118e
180 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The file is an OLE document with a significant amount of slack space, indicating it may be used to hide malicious content. Heuristics indicate the use of APIs like ShellExecute, VirtualAlloc, LoadLibrary, and GetProcAddress, which are commonly used by malware to load and execute payloads. No document body or script content was available for further analysis.

Heuristics 5

  • Reference to ShellExecute API high SC_STR_SHELLEXEC
    Reference to ShellExecute 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 308,672 bytes but its declared streams total only 31,351 bytes — 277,321 bytes (90%) 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

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