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

Static analysis result for SHA-256 f109449acbfed7d5…

MALICIOUS

Office (OLE) / .DOC

229.4 KB
MD5: 302b3d5455d5f4194a28139b2e2161fc SHA-1: f59e4a2779415ac046bf40cb16cc1816a3234c52 SHA-256: f109449acbfed7d585f90b5333f51988c03168b3b37f6138932b1904245554a2
340 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File T1055.012 Process Hollowing T1055.001 Process Injection

The sample contains numerous high and critical heuristic firings related to process injection techniques, including CreateProcess, VirtualAlloc, WriteProcessMemory, CreateRemoteThread, LoadLibrary, and GetProcAddress. This strongly suggests the document is designed to inject malicious code into a legitimate process. The embedded URL is likely used to download a second-stage payload. The OLE slack anomaly and NOP sled further indicate a packed or obfuscated 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
  • NOP sled detected high SC_NOP_SLED
    Found 20+ consecutive 0x90 bytes
  • 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 234,888 bytes but its declared streams total only 31,351 bytes — 203,537 bytes (87%) 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
  • 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.winimage.com/zLibDll