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

Static analysis result for SHA-256 81041778c79aa4a4…

MALICIOUS

Office (OOXML) / .XLSX

26.5 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: 81ed66006dd3a5b2f1caa94b073c368a SHA-1: 6d5fd3cf7b113cf8795cbc5c78437f6ada067c72 SHA-256: 81041778c79aa4a4b21db0713da712262ecea27aa274d4381bce9d390d585f13
182 Risk Score

Malware Insights

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

The file contains Excel 4.0 macros, identified by the OOXML_XLM_MACROSHEET heuristic. These macros utilize WinAPI functions like URLDownloadToFileA and ShellExecuteA, as indicated by OOXML_XLM_BINARY_WINAPI_STRINGS. The primary function appears to be downloading a payload from the URL https://mfruits.co/ds/4.gif and executing it, which is a common technique for delivering further malware.

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://mfruits.co/ds/4.gif

Extracted artifacts 1

Files carved from inside the sample during analysis.

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

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