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

Static analysis result for SHA-256 1de6bb6f11cdd342…

MALICIOUS

Office (OLE) / .DOC

167.0 KB
MD5: 903ec28ee272fc8b62d6cbf95f27c6d6 SHA-1: dfe52c1a9b3707326991ead5340ea7dd0610c003 SHA-256: 1de6bb6f11cdd342f64c711e175f6df1ff33187f3e178dc4f3362a3addbf2210
220 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File T1027 Obfuscated Files or Information

The sample is a malicious OLE document with a significant slack space anomaly, indicating potential obfuscation or embedded malicious content. Heuristics indicate the use of Windows API functions commonly associated with malware execution (WinExec, LoadLibrary, GetProcAddress) and XOR-encoded strings, suggesting the file attempts to load and run additional code. The document body contains references to embedded Office objects, further supporting the execution of malicious payloads.

Heuristics 5

  • XOR-encoded strings (key 0x03) critical SC_XOR_ENCODED
    Found 8 Windows library/API name(s) XOR-encoded with single-byte key 0x03: 'VirtualAlloc', 'VirtualAlloc', 'VirtualAllocEx', 'VirtualProtect', 'VirtualProtectEx', 'CreateProcessA', 'WriteProcessMemory', 'ReadProcessMemory'
  • Reference to WinExec API high SC_STR_WINEXEC
    Reference to WinExec 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 171,008 bytes but its declared streams total only 31,351 bytes — 139,657 bytes (82%) 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).