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

Static analysis result for SHA-256 1cae3289abbb2f4f…

MALICIOUS

Office (OLE) / .DOC

118.3 KB Created: 2007-09-18 04:34:00 Authoring application: Microsoft Word 11.
MD5: 07661d8a078bb60f45439ef51853cfc5 SHA-1: 751a98f81998d227c4fb9c20ab71fbc6eb4e7954 SHA-256: 1cae3289abbb2f4fb6ef707caeb63f3e41af14e9898f83d9f39bad78974162f8
220 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1059.003 Windows Command Shell T1059.006 Python T1059.010 Java

The sample exhibits high-severity heuristic firings indicating the use of WinExec, CreateProcess, and ShellExecute APIs, suggesting an attempt to execute arbitrary code. A critical heuristic identified XOR-encoded strings (key 0xCE), which are commonly used for obfuscation. The presence of a large slack space anomaly in the OLE structure further supports a suspicious nature. While no document body text was readable, the combination of API calls and obfuscation techniques points to a downloader or dropper functionality.

Heuristics 5

  • XOR-encoded strings (key 0xCE) critical SC_XOR_ENCODED
    Found 5 Windows library/API name(s) XOR-encoded with single-byte key 0xCE: 'CreateProcessA', 'CreateFileA', 'OpenProcess', 'RegOpenKeyExA', 'ShellExecuteA'
  • Reference to WinExec API high SC_STR_WINEXEC
    Reference to WinExec API
  • Reference to CreateProcess API high SC_STR_CREATEPROCESS
    Reference to CreateProcess API
  • Reference to ShellExecute API high SC_STR_SHELLEXEC
    Reference to ShellExecute API
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 121,182 bytes but its declared streams total only 16,486 bytes — 104,696 bytes (86%) 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).

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