Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 06b947e519fc9acc…

MALICIOUS

Office (OLE)

142.0 KB
MD5: a50199a459ea5f767aaac8294c6a8939 SHA-1: 6ef1e3aa770c1cc82429f0d7d423bffb49a28e76 SHA-256: 06b947e519fc9acc93b757e1f362e4c3c05e716a722da7efca6342e0b3afb4bb
380 Risk Score

Malware Insights

MITRE ATT&CK
T1059.003 Windows Command Shell T1204.002 Malicious File T1566.001 Spearphishing Attachment

The sample is an OLE document exhibiting a large slack space anomaly and containing an EMF object within an EPRINT stream, indicative of malicious structuring. High-severity heuristics indicate the use of PEB API-hash resolution, WinExec, VirtualAlloc, LoadLibrary, and GetProcAddress, strongly suggesting the execution of shellcode. Furthermore, a suspicious invocation of cmd.exe with an execution flag was detected, pointing towards the execution of a secondary payload.

Heuristics 10

  • Office EPRINT stream contains EMF object high CVE related OLE_EPRINT_EMF_OBJECT
    OLE ObjectPool contains an EPRINT stream with EMF data. This is rare in normal documents and is CVE-2007-3893/MS07-046-family evidence when paired with Office exploit payload anomalies, but the malformed EMF record is not proven by this rule alone.
  • x86 GetPC stub (CALL $+5; POP EAX) high SC_GETPC_CALL
    x86 GetPC stub (CALL $+5; POP EAX)
  • PEB access via FS segment (x86) high SC_PEB_ACCESS
    PEB access via FS segment (x86)
  • PEB API-hash resolver high SC_API_HASH_RESOLVER
    PEB access followed by ROR13-style API hashing, a common position-independent shellcode import resolver
  • Reference to WinExec API high SC_STR_WINEXEC
    Reference to WinExec API
  • Suspicious cmd.exe invocation with execution flag high SC_STR_CMD
    Suspicious cmd.exe invocation with execution flag
  • 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 145,408 bytes but its declared streams total only 31,351 bytes — 114,057 bytes (78%) 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).
  • Reference to VirtualAlloc API medium SC_STR_VIRTUALALLOC
    Reference to VirtualAlloc API

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