Xls.Trojan.Laroux-28 — Office (OLE) / .EXE malware analysis

Static analysis result for SHA-256 61081a2367a0062d…

MALICIOUS

Office (OLE) / .EXE

52.5 KB Authoring application: Microsoft Excel
MD5: b4ee9f8b028a87dd31b00b0dba3bd708 SHA-1: 47df15c606872f9d18b29a0ce3f5203e9166dd03 SHA-256: 61081a2367a0062d5d4f7c8129120702349aed2fa9d5501ac2f40b84c110377e
240 Risk Score

Malware Insights

Xls.Trojan.Laroux-28 · confidence 95%

MITRE ATT&CK
T1059.005 Visual Basic T1566.001 Spearphishing Attachment

The file is identified as a malicious Excel 5 Laroux macro virus, specifically 'Xls.Trojan.Laroux-28'. The Auto_Open macro is configured to execute the 'check_files' subroutine upon opening, which attempts to save a file named 'PLDT.XLS' in the startup path and potentially execute it. This indicates a classic macro-based malware delivery mechanism.

Heuristics 5

  • Excel 5 Laroux/Larou-CV macro-virus marker cluster critical OLE_XLS5_LAROUX_MACRO_VIRUS
    Legacy Excel workbook contains a Laroux/Larou-CV macro-virus marker cluster including auto_open execution and workbook/module replication strings. This is a narrow indicator for an infected legacy Excel macro workbook.
  • ClamAV: Xls.Trojan.Laroux-28 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Xls.Trojan.Laroux-28
  • 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.
  • Auto_Open macro high OLE_VBA_AUTO
    Auto_Open macro
  • VBA macros detected medium OLE_VBA_MACROS
    Document contains VBA macro code

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas
50eb218165da9c199f0da673535dfc58834adfce400c4528b4b7665205671be2		 vba-macro oletools.olevba.extract_macros (decoded VBA source) 1967 bytes
Detection
ClamAV: Xls.Trojan.Laroux-28
Obfuscation or payload: unlikely

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