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

Static analysis result for SHA-256 8e6c446715333057…

MALICIOUS

Office (OLE) / .PPS

405.0 KB Created: 2002-10-18 01:18:54 Authoring application: Microsoft PowerPoint
MD5: b8edd4ff4faa43c81abdd376cec8fed0 SHA-1: 413dd6f389ea690d771b7ba0c8226ccec7f9ae8b SHA-256: 8e6c446715333057c03af9c528c6b16798e683a258d592e0e09d07a9ea97fb4d
82 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The file is a PowerPoint presentation (PPS) that contains a chain letter lure in its document body, promising luck and wealth upon forwarding. Static analysis detected an appended executable payload and significant slack space within the OLE structure, indicating the presence of hidden malicious content. VBA macros could not be extracted due to an unsupported format, but the appended payload suggests the file is designed to deliver a secondary stage. The primary attack vector appears to be social engineering via the document content, with the appended payload indicating a malicious intent beyond the chain letter itself.

Heuristics 3

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 414,720 bytes but its declared streams total only 198,577 bytes — 216,143 bytes (52%) 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.
  • Unsupported Office format for VBA extraction info OFFICE_FORMAT_UNSUPPORTED
    olevba could not extract VBA macros (PermissionError); format-agnostic byte-level scans still ran. Likely legacy, encrypted, or malformed OLE/OOXML — re-scanning the same bytes will yield the same outcome.