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

Static analysis result for SHA-256 25583c17cbb896e2…

MALICIOUS

Office (OLE) / .DOC

62.4 KB Created: 2006-01-25 08:30:00 Authoring application: Microsoft Office Word
MD5: 26b53f9f0c324de62754c9cbc2738226 SHA-1: 553daa33ae06fb19d45db6583dfce751fbaff65f SHA-256: 25583c17cbb896e214e91cc0936ee2a8b40ef590070a2e83e6bae9afdf426313
140 Risk Score

Malware Insights

The OLE document exhibits a significant slack space anomaly, indicating it may be a container for malicious code. Heuristic firings related to VirtualProtect, LoadLibrary, and GetProcAddress APIs suggest the presence of shellcode designed to dynamically load and execute code. No document body or script content was available for further analysis.

Heuristics 4

  • 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 63,904 bytes but its declared streams total only 21,151 bytes — 42,753 bytes (67%) 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 VirtualProtect API medium SC_STR_VIRTUALPROTECT
    Reference to VirtualProtect API

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