Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 b618984ede66736d…

MALICIOUS

Office (OLE)

68.9 KB Created: 2006-01-25 08:30:00 Authoring application: Microsoft Office Word
MD5: 240721e9f6899b8397007ea7b7b55f56 SHA-1: 7ac2270a86dec1856b5623b11d84cc72966a566d SHA-256: b618984ede66736d03297ab8408936df2d51fe9ba6b0370e47b167724e66fa38
400 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1055 Process Injection T1105 Ingress Tool Transfer

The file is an OLE document with a significant slack space anomaly and an embedded PE executable. Critical heuristics indicate the use of WriteProcessMemory and CreateRemoteThread, suggesting process injection. High-severity heuristics point to CreateProcess, VirtualAlloc, LoadLibrary, and GetProcAddress, which are commonly used by droppers to load and execute malicious payloads. The ClamAV detection as 'Doc.Dropper.Agent' further supports this. The embedded executable and process injection techniques strongly indicate a dropper functionality designed to download and execute a second-stage 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
  • ClamAV: Doc.Dropper.Agent-7119440-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Dropper.Agent-7119440-0
  • 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 70,560 bytes but its declared streams total only 21,151 bytes — 49,409 bytes (70%) 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