Malicious Office (OOXML) / .XLSX — malware analysis report

Static analysis result for SHA-256 a4ea0f5a8dd46350…

MALICIOUS

Office (OOXML) / .XLSX

26.3 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: 87763afa25a024ac93b2ae73ee8331e4 SHA-1: 07b87a971a3b9bb8b98380e65871b5d102afb2fc SHA-256: a4ea0f5a8dd46350a224befd3abbe838c305b6250fbeb8efb61e22c7eafc8fa8
182 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Service Execution: Visual Basic T1204.002 Malicious File: User Execution: Malicious File T1105 Ingress Tool Transfer

This Excel file contains a binary Excel 4.0 macro sheet that leverages WinAPI functions such as URLDownloadToFileA and ShellExecuteA. The macro reconstructs the URL http://puroraw.com/ds/3.gif, indicating its intent to download and execute a second-stage payload. The presence of these functions and the reconstructed URL strongly suggest a downloader or droppper functionality.

Heuristics 4

  • Excel 4.0 macro sheet (1 sheet(s)) critical OOXML_XLM_MACROSHEET
    Spreadsheet contains an Excel 4.0 (XLM) macro sheet — XLM was a major Office malware vector during 2020-2022 and evaded many VBA-focused controls before Microsoft tightened XLM defaults. Even legitimate XLM use is rare in modern workbooks. The macro sheet is stored as XLSB/BIFF12 binary content, which many XML-only OOXML scanners miss.
  • Binary XLM macro sheet with WinAPI/download strings critical OOXML_XLM_BINARY_WINAPI_STRINGS
    Excel 4.0 macro sheet is stored as BIFF12/XLSB binary data and contains Win32 download or process-execution API strings such as URLDownloadToFileA, ShellExecuteA, or CreateDirectoryA. These strings are high-signal in XLM macro sheets and catch payload-download macros that XML-formula scanners cannot parse.
  • URL reconstructed from XLM cell array (1 URL) critical OOXML_XLM_CELL_ARRAY_URL
    Excel 4.0 macro sheet stages its payload URL across individual numeric cells (one ASCII charcode per cell) or inside an embedded HTA that uses VBScript Chr()/&-concat obfuscation. The reconstructed URL is invisible to literal-bytes URL extraction because it is never contiguous in the workbook stream. URLs were recovered by walking the BIFF12 record stream of every worksheet and macrosheet part and decoding RK/inline-string cells in both row-major and column-major order.
  • 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://puroraw.com/ds/3.gif

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
bcb2a00478b552ea7aa0ba3395a02a282bd76772458f85092b2d3253d326ab01		 xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 200414 bytes

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