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

Static analysis result for SHA-256 4e9f488d86e52378…

MALICIOUS

Office (OLE) / .DOC

1.05 MB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 6388b9fc206c1f5fedeb969d79161c18 SHA-1: 6a5bfd9ddf9b665ec860982a5130122b2d01e2ec SHA-256: 4e9f488d86e52378d1fa298db30911ca1df7e878323f727ba7915203633c7ed8
280 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File T1055.012 Process Hollowing T1055.001 Process Injection T1105 Ingress Tool Transfer

The sample exhibits critical heuristic firings for WriteProcessMemory and CreateRemoteThread, along with high-confidence firings for LoadLibrary and GetProcAddress. These indicate the sample is likely injecting code into another process. The presence of VirtualAlloc and VirtualProtect further supports memory manipulation for execution. The OLE slack anomaly suggests hidden or packed data within the file. While no specific script was extracted, the combination of API calls strongly suggests a shellcode loader designed to download and execute a second-stage payload, likely from a remote source. The embedded URL 'http://www.iec.ch' is flagged as benign but could be a fallback or part of a larger infrastructure.

Heuristics 8

  • Reference to WriteProcessMemory API critical SC_STR_WRITEPROCESSMEMORY
    Reference to WriteProcessMemory API
  • Reference to CreateRemoteThread API critical SC_STR_CREATEREMOTETHREAD
    Reference to CreateRemoteThread 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 1,096,192 bytes but its declared streams total only 94,801 bytes — 1,001,391 bytes (91%) 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
  • Reference to VirtualProtect API medium SC_STR_VIRTUALPROTECT
    Reference to VirtualProtect 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://ns.adobe.com/xap/1.0/
    • http://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://ns.adobe.com/xap/1.0/mm/
    • http://ns.adobe.com/xap/1.0/sType/ResourceRef#
    • http://purl.org/dc/elements/1.1/
    • http://ns.adobe.com/photoshop/1.0/
    • http://ns.adobe.com/tiff/1.0/
    • http://ns.adobe.com/exif/1.0/
    • http://ns.adobe.com/xap/1.0/sType/ResourceEvent#
    • http://www.iec.ch

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