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

Static analysis result for SHA-256 3176fa74522d9aa0…

MALICIOUS

Office (OLE) / .DOC

142.4 KB Created: 2006-01-25 08:30:00 Authoring application: Microsoft Office Word
MD5: 78a3677f5a563fd6f2439a4af5419027 SHA-1: 28693b59e25779aab1cbb82dfc13faa1d9197029 SHA-256: 3176fa74522d9aa0e4a7fe3d65b5b4d6904922eecb0f00aff3c2a1be389375ec
220 Risk Score

Malware Insights

MITRE ATT&CK
T1059 Command and Scripting Interpreter T1204 User Execution T1059.003 Windows Command Shell

The sample exhibits high-confidence heuristic firings for CreateProcess, ShellExecute, LoadLibrary, and GetProcAddress, indicating an attempt to execute arbitrary code. The OLE slack anomaly suggests potential obfuscation or embedded malicious content. While no scripts were extracted, the API calls strongly suggest the document is designed to download and execute a second-stage payload, likely via the unknown reputation URL. The document body content is obfuscated and does not provide further clues.

Heuristics 7

  • Reference to CreateProcess API high SC_STR_CREATEPROCESS
    Reference to CreateProcess API
  • Reference to ShellExecute API high SC_STR_SHELLEXEC
    Reference to ShellExecute 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 145,824 bytes but its declared streams total only 21,151 bytes — 124,673 bytes (85%) 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
  • 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.finance.gov.pk/admin/images/budget/Budget%20in%20Brief%202009-10.pdf
    • http://news.xinhuanet.com/english2010/china/2010-03/04/c_13196769.htm