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

Static analysis result for SHA-256 434b98e5f4db77b1…

MALICIOUS

Office (OLE) / .DOC

110.0 KB
MD5: 280b79c4fbf098ddd52756eb7954289f SHA-1: cc5d3100af690783994d33a36082b0cb3e81df35 SHA-256: 434b98e5f4db77b1238c50ee97f76a23737bccf11f528f9e2fca3d43932c1059
460 Risk Score

Malware Insights

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

The sample exhibits characteristics of a malicious OLE document, including a large slack space anomaly and an embedded PE executable. High-severity heuristics indicate the use of Windows API functions such as WriteProcessMemory and CreateRemoteThread, strongly suggesting process injection capabilities. The presence of an embedded executable further supports the likelihood of code execution. While one URL was extracted, it was labeled as benign.

Heuristics 12

  • 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 WinExec API high SC_STR_WINEXEC
    Reference to WinExec API
  • Reference to CreateProcess API high SC_STR_CREATEPROCESS
    Reference to CreateProcess API
  • Reference to ShellExecute API high SC_STR_SHELLEXEC
    Reference to ShellExecute 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 112,640 bytes but its declared streams total only 31,351 bytes — 81,289 bytes (72%) 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).
  • Embedded PE executable high OLE_EMBEDDED_EXE
    MZ/PE header found inside document — possible embedded executable
  • 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://spaces.brad.ac.uk:8080/display/ssispsru/Contact