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

Static analysis result for SHA-256 c0fdd800de3550bf…

MALICIOUS

Office (OLE) / .DOC

460.0 KB
MD5: a427804e0b3af9d62e871ad4b0f999ab SHA-1: 0adcc5757a8c298d4c98290daf8e698ff7757947 SHA-256: c0fdd800de3550bf7b4b2d2ab03db29210b7f4eddf266dec3c1cc712d07cc271
160 Risk Score

Malware Insights

MITRE ATT&CK
T1059 Command and Scripting Interpreter T1204 Malicious Link

The presence of a NOP sled, references to LoadLibrary and GetProcAddress APIs, and a large slack space anomaly in the OLE structure strongly indicate the file is designed to execute shellcode. The embedded URLs likely serve as download locations for further payloads. No scripts were extracted from this sample, limiting the ability to detail the exact execution flow.

Heuristics 5

  • NOP sled detected high SC_NOP_SLED
    Found 20+ consecutive 0x90 bytes
  • 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 471,040 bytes but its declared streams total only 31,351 bytes — 439,689 bytes (93%) 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 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://www.5iantlavalamp.com/Z
    • http://www.5iantlavalamp.com/V
    • http://www.5iantlavalamp.com/

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