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

Static analysis result for SHA-256 0873c1b382f8de91…

MALICIOUS

Office (OOXML) / .XLSX

26.3 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: 4f40afd624d5106ee32f87aeb93d861a SHA-1: 2892428571b4633d5f4b4eef2c0d095d1cc5f8ce SHA-256: 0873c1b382f8de91424e0447fcd91bf35b2d5ef279dc82eec31274f9717913eb
242 Risk Score

Malware Insights

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

The file contains Excel 4.0 macros, identified by the OOXML_XLM_MACROSHEET heuristic. These macros are designed to download and execute a payload, as indicated by the presence of WinAPI strings like URLDownloadToFileA and ShellExecuteA. The macro reconstructs URLs, including https://absolutefitnessgym.com/ and https://absolutefitnessgym.com/ds/3.gif, which are likely used to fetch the secondary stage. The use of these functions and the reassembled URLs strongly suggest an attempt to download and run a malicious executable.

Heuristics 5

  • 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.
  • XLM payload reassembled from CHAR()/split formulas critical OOXML_XLM_REASSEMBLED_PAYLOAD
    An Excel 4.0 macro sheet builds its payload inside the formula token stream by concatenating per-character CHAR() calls and string fragments, so no WinAPI name, shell command, or URL is ever contiguous in the .bin for a literal-bytes scan to find. Reassembling the formulas recovered download/execute API names, LOLBin commands (regsvr32/rundll32/mshta/wmic/powershell), or a payload URL — the de-obfuscated download-and-run kill chain.
  • URL reconstructed from XLM cell array (2 URLs) 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://absolutefitnessgym.com/
    • https://absolutefitnessgym.com/ds/3.gif

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
33b39070cf703fb8920ce299136e91bbc3d2e0dae01e819c4b64ba4e4c896109		 xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 200463 bytes

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