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

Static analysis result for SHA-256 e20bf8e88b2275cd…

MALICIOUS

Office (OLE) / .DOC

127.5 KB Created: 2006-01-25 08:30:00 Authoring application: Microsoft Office Word
MD5: d825cf2dd4392c0f9b6e8e4f801bf8f4 SHA-1: cf811792d7f7e7614d22982fec064b0df32938fc SHA-256: e20bf8e88b2275cd3a645bb4ba81586ccd39c078596926ad67b49e07e4610901
360 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1059.003 Windows Command Shell T1055 Process Injection T1105 Ingress Tool Transfer

The sample exhibits high-confidence heuristics related to process injection (WriteProcessMemory, CreateRemoteThread) and dynamic library loading (LoadLibrary, GetProcAddress), strongly suggesting it attempts to inject code into another process. References to WinExec and CreateProcess indicate the execution of external commands or payloads. The OLE slack anomaly suggests potential obfuscation or padding within the document structure. No document body or script content was available for further analysis, limiting the ability to determine the exact delivery mechanism or payload.

Heuristics 9

  • Reference to WriteProcessMemory API critical SC_STR_WRITEPROCESSMEMORY
    Reference to WriteProcessMemory API
  • Reference to CreateRemoteThread API critical SC_STR_CREATEREMOTETHREAD
    Reference to CreateRemoteThread API
  • Reference to WinExec API high SC_STR_WINEXEC
    Reference to WinExec API
  • 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 130,562 bytes but its declared streams total only 21,151 bytes — 109,411 bytes (84%) 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

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