Malicious Office (OLE) / .-CH — malware analysis report

Static analysis result for SHA-256 6ab05071616c3371…

MALICIOUS

Office (OLE) / .-CH

356.1 KB
MD5: 24fdce198c4c0496ae23c8cef11baa0a SHA-1: 9e65ced91dc8bb1795908b5a438a56856d79e33a SHA-256: 6ab05071616c33716489bca9282769477f7379ca816f68ba10d85a7d52450133
80 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The OLE document exhibits significant slack space and an appended executable payload, strongly suggesting it's a container for malicious code. The presence of these anomalies points towards a malicious OLE file designed to deliver a secondary payload upon opening or interaction. The file's structure is indicative of a common technique for obfuscating or hiding malicious content.

Heuristics 2

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 364,692 bytes but its declared streams total only 12,447 bytes — 352,245 bytes (97%) 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).
  • OLE file has appended executable-looking payload bytes high OLE_APPENDED_PAYLOAD
    OLE compound file contains a large high-entropy region beyond the declared major streams and that region includes shellcode, PE, or loader API markers. This is a payload-carrier signal, not a specific CVE attribution by itself.