Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 76cffe46acbc3a48…

MALICIOUS

Office (OLE)

81.8 KB Created: 2006-01-25 08:30:00 Authoring application: Microsoft Office Word
MD5: d279340ebec911506e273a1f93323a87 SHA-1: e6f72abc57a7f66817a7a82c77fe70488b927166 SHA-256: 76cffe46acbc3a48510e386c43e40aff1887b9764122a146a7ea77a6145929d5
340 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The sample is an OLE document exhibiting characteristics of malicious intent, including a large slack space anomaly and references to critical Windows API functions for process execution and memory allocation. The presence of heuristics related to PEB access and API hash resolution suggests sophisticated evasion techniques. While no specific document body content or scripts were extracted, the API calls strongly indicate the file's purpose is to download and execute a second-stage payload.

Heuristics 9

  • x86 GetPC stub (CALL $+5; POP EAX) high SC_GETPC_CALL
    x86 GetPC stub (CALL $+5; POP EAX)
  • PEB access via FS segment (x86) high SC_PEB_ACCESS
    PEB access via FS segment (x86)
  • PEB API-hash resolver high SC_API_HASH_RESOLVER
    PEB access followed by ROR13-style API hashing, a common position-independent shellcode import resolver
  • 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 83,813 bytes but its declared streams total only 21,151 bytes — 62,662 bytes (75%) 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.