Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 450370dfac39ad92…

MALICIOUS

Office (OLE)

192.3 KB First seen: 2015-10-06
MD5: 7cc7c23f0b2c99772ea4fbceee035bc0 SHA-1: eeee488bdcbc7085eb710c87b68f8772ff2157ef SHA-256: 450370dfac39ad92668ce64d9a1c6621f17bc6881d12f2e75d68dcf2c7d2278e
220 Risk Score

Heuristics 5

  • ClamAV: Win.Dropper.Small-1957 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Dropper.Small-1957
  • 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 196,889 bytes but its declared streams total only 12,184 bytes — 184,705 bytes (94%) 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.

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