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

Static analysis result for SHA-256 4b228e563bfb62f7…

MALICIOUS

Office (OLE) / .DO

228.0 KB
MD5: 8f03c5fc69af0cc9cb76c9d9b6fcd06b SHA-1: b8608d3d5af46331ecd6ce90cc4cc7ca5138aff5 SHA-256: 4b228e563bfb62f702bfbef8a6eea9d3ba23bf647e0d9ab5044070a77385fc2a
140 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1027 Obfuscated Files or Information

The sample exhibits characteristics of a malicious document, including a NOP sled and XOR-encoded strings, indicating an attempt to hide malicious code. The OLE document structure also shows a significant amount of slack space, which is often used for obfuscation or embedding additional content. While no specific family is identified, the techniques used point towards a downloader or dropper attempting to conceal its payload.

Heuristics 3

  • XOR-encoded strings (key 0xC6) critical SC_XOR_ENCODED
    Found 7 Windows library/API name(s) XOR-encoded with single-byte key 0xC6: 'KERNEL32.DLL', 'iphlpapi.dll', 'LoadLibraryA', 'GetProcAddress', 'VirtualAlloc', 'VirtualProtect', 'ExitProcess'
  • NOP sled detected high SC_NOP_SLED
    Found 20+ consecutive 0x90 bytes
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 233,472 bytes but its declared streams total only 129,793 bytes — 103,679 bytes (44%) 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).