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

Static analysis result for SHA-256 05aa485c6efbef1c…

MALICIOUS

Office (OOXML) / .XLSM

23.2 KB Created: 2015-06-05 18:17:20 UTC Authoring application: Microsoft Excel 16.0300 First seen: 2022-04-21
MD5: f934fa86a858b351f6f84b7f07577011 SHA-1: e7d4faa249f33e4c127b3236d62faa422b7097db SHA-256: 05aa485c6efbef1c65e5876428d00cbb72b85b0c16530ec9f0ed47355f8189d6
330 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1204.002 Malicious File

The sample is an XLSM file containing a Workbook_Open macro that executes a command using Wscript.Shell. The command uses mshta.exe to download and execute a second-stage payload from the URL "https://bitbucket.org/!api/2.0/snippets/hogya/M9xe79/890b898167a2c0437e6c07c6ef3027af53541881/files/mrxxx". This indicates a downloader or droppper functionality.

Heuristics 9

  • Shell() call in VBA critical OLE_VBA_SHELL
    Shell() call in VBA
  • ClamAV: Xls.Trojan.Generic-9994593-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Xls.Trojan.Generic-9994593-0
  • ClamAV detection on extracted artifact critical EXTRACTED_FILE_CLAMAV
    ClamAV flagged at least one file extracted from inside this sample. Even when the wrapping document carries no AV detection of its own, a hit on the carved artifact is a strong indicator the sample is a delivery vehicle.
  • Workbook_Open macro high OLE_VBA_WBOPEN
    Workbook_Open macro
  • VBA p-code auto-exec with execution tokens high OLE_VBA_PCODE_AUTOEXEC_EXEC
    Compiled VBA/cache stream contains an auto-execution token together with shell/download/object-execution tokens. This catches p-code-only or source-extraction-failure macro documents where visible source is unavailable.
  • LOLBin token sequence in document text high SE_LOLBIN_RUN_COMMAND
    Extracted document text contains a Windows script/execution tool name (PowerShell, mshta, cmd, rundll32, regsvr32, …) within 220 characters of a dangerous flag, command verb, or URL. This is a visible 'run this' instruction in HTML/PDF/RTF lure bodies, or — in macro-laden Office files — the macro's own string-pool entries appearing adjacent in extracted text.
  • VBA project inside OOXML medium OOXML_VBA
    Document contains a VBA project — VBA macros present
  • Hidden worksheet (hidden) low OOXML_HIDDEN_SHEET
    Excel workbook contains 2 hidden sheet(s) — hidden sheets are commonly used to conceal macro code, staging data, or intermediate payload construction
  • 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://bitbucket.org/!api/2.0/snippets/hogya/M9xe79/890b898167a2c0437e6c07c6ef3027af53541881/files/mrxxx

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas
41a079f302469a7cad088ef88057e74da7df11923bb5bb2605fd6d143d93bb3c		 vba-macro oletools.olevba.extract_macros (decoded VBA source from OOXML) 2546 bytes
vbaProject_00.bin
492d4627fa6643fd3767c20c62ff4bbeb20219f936333ad389b515de7abb5bf7		 vba-project OOXML VBA project: xl/vbaProject.bin 34816 bytes
Detection
ClamAV: Xls.Trojan.Generic-9994593-0
Obfuscation or payload: unlikely

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