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

Static analysis result for SHA-256 d2966261159f9146…

MALICIOUS

Office (OOXML) / .XLSX

26.5 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: 77a1f49ea7c6eb2cdf9e6f187c5fca34 SHA-1: ae39e789d676044e0e14f5429bbee07978393682 SHA-256: d2966261159f914625e85ced29ae8c1cc42f7db14f2fca72f8981a951ba1eb3e
182 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic for Applications T1204.002 Malicious File T1105 Ingress Tool Transfer

This Excel file contains critical Excel 4.0 macros, including strings indicative of WinAPI calls like URLDownloadToFileA and ShellExecuteA. The macros reconstruct a URL, https://ruth.co.il/ds/4.gif, which is likely used to download and execute a second-stage payload. The presence of these WinAPI strings and the reconstructed URL strongly suggests 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 https://ruth.co.il/ds/4.gif

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
0e69ba788cb3ffb490d766a0bc85cd4b0a0356528b4e74b33b0d6e539f811dc9
xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 197528 bytes