Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 c5509b362f6dfb03…

MALICIOUS

Office (OLE)

122.5 KB
MD5: 7a518e2b5856c3f4ef37ee1c2a6d86fc SHA-1: 6dcaf0baf380d2a446b58ee8f3d72ef7c01eac06 SHA-256: c5509b362f6dfb038ca5bf2ae6ac0399a296bc5ca6eada0f980e9d54b8a71174
220 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1059.003 Windows Command Shell T1105 Ingress Tool Transfer T1027 Obfuscated Files or Information

The sample exhibits characteristics of a malicious Office document, including XOR-encoded strings and references to Windows API functions like WinExec, LoadLibrary, and GetProcAddress. The presence of OLE slack space anomaly and embedded URLs, though benign in this instance, further supports a malicious intent. The obfuscated nature of the strings and the API calls suggest the document is designed to download and execute a second-stage payload.

Heuristics 6

  • XOR-encoded strings (key 0x11) critical SC_XOR_ENCODED
    Found 1 Windows library/API name(s) XOR-encoded with single-byte key 0x11: 'kernel32.dll'
  • Reference to WinExec API high SC_STR_WINEXEC
    Reference to WinExec API
  • 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 125,440 bytes but its declared streams total only 56,346 bytes — 69,094 bytes (55%) 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).
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://www.microsoft.com
    • https://www.verisign.com/rpa
    • http://ocsp.verisign.com/ocsp/status0
    • https://www.verisign.com/rpa0
    • http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl0

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