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

Static analysis result for SHA-256 f7ccfae4996af1ab…

MALICIOUS

Office (OLE) / .DOC

216.1 KB Created: 2006-04-29 01:29:00 Authoring application: Microsoft Office Word
MD5: 57ab95faf24fc4cefc3b7bd0b73cd176 SHA-1: d21b6ab24c1aa91eb7dc18df0f389260d05ba39c SHA-256: f7ccfae4996af1ab7d43b535688f039afb4720431c99940928905d53c5863eb1
322 Risk Score

Malware Insights

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

The file is a malicious Microsoft Word document detected by ClamAV as Win.Exploit.MSWord-6. Heuristics indicate the presence of a NOP sled, and API calls such as CreateProcess, VirtualAlloc, LoadLibrary, and GetProcAddress suggest the document is designed to load and execute shellcode. The large slack space and appended payload further support this. No document body or script content was available for analysis, limiting the ability to determine the exact payload or delivery mechanism.

Heuristics 9

  • ClamAV: Win.Exploit.MSWord-6 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Exploit.MSWord-6
  • 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 221,282 bytes but its declared streams total only 26,783 bytes — 194,499 bytes (88%) 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).
  • OLE file has appended executable-looking payload bytes high OLE_APPENDED_PAYLOAD
    OLE compound file contains a large high-entropy region beyond the declared major streams and that region includes shellcode, PE, or loader API markers. This is a payload-carrier signal, not a specific CVE attribution by itself.
  • Reference to VirtualAlloc API medium SC_STR_VIRTUALALLOC
    Reference to VirtualAlloc API
  • Unsupported Office format for VBA extraction info OFFICE_FORMAT_UNSUPPORTED
    olevba could not extract VBA macros (PermissionError); format-agnostic byte-level scans still ran. Likely legacy, encrypted, or malformed OLE/OOXML — re-scanning the same bytes will yield the same outcome.

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