Malicious Office (OLE) / .XLS — malware analysis report

Static analysis result for SHA-256 81de08ff7242ecb1…

MALICIOUS

Office (OLE) / .XLS

525.5 KB Created: 2006-09-16 00:00:00 Authoring application: Microsoft Excel First seen: 2026-05-23
MD5: 6c12e802b83b2c89c5765a2f3e5d6de5 SHA-1: f6382e83be2207f094a6c17a8dac6341bf34e592 SHA-256: 81de08ff7242ecb11e17c594c7f0684d08250a79405d98fc1e56f5d11cbe4596
102 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1059.005 Visual Basic T1204.002 Malicious File

The sample is an Excel 4.0 (XLM) macro-enabled workbook. It contains an 'enable-content' lure, instructing the user to enable macros, which is a common technique for malware droppers. The embedded macros likely download and execute a second-stage payload from one of the provided URLs, such as https://kashishbd.com/qLQ59E1q2/solo.html.

Heuristics 4

  • XLM Auto_Open workbook with payload URL or enable-content lure critical OLE_XLM_AUTOOPEN_PAYLOAD_LURE
    Workbook contains an Excel 4.0 macro sheet with Auto_Open / Auto_Close and also exposes a payload URL or enable-content lure in the OLE bytes. This combination is a high-confidence XLM downloader/social-engineering pattern even when formula recovery cannot decode the full macro chain.
  • Excel 4.0 (XLM) macro sheet present medium OLE_XLM_AUTOOPEN
    Workbook contains an Excel 4.0 macro sheet sub-stream — XLM is rarely seen in modern legitimate workbooks and was a major Office malware vector during 2020-2022.
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings
  • 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://kashishbd.com/qLQ59E1q2/solo.html In document text (OLE body)
    • https://maatdeur.com/aTmGQK0DBT/solo.htmlIn document text (OLE body)