Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 1b4986c9d37399ce…

MALICIOUS

Office (OLE)

88.3 KB Created: 2006-01-25 08:30:00 Authoring application: Microsoft Office Word
MD5: 423555bae5683757fcd0f32c3512acc4 SHA-1: 114ea72fe6241823785a552733197fd82a0e63fb SHA-256: 1b4986c9d37399ce421f46cdc53f6c1f41e3f6bec7c879fb7f351b0a64d6b172
340 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1059.003 Windows Command Shell T1204.002 Malicious File

The sample exhibits high-confidence heuristics indicating the presence of API hashing and dynamic API resolution, commonly used to evade detection. References to WinExec, CreateProcess, VirtualAlloc, LoadLibrary, and GetProcAddress suggest the file is designed to load and execute arbitrary code. The large slack space in the OLE structure is also anomalous and may be used to hide malicious components. No document body or script content was available for further analysis.

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 90,469 bytes but its declared streams total only 21,151 bytes — 69,318 bytes (77%) 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.