Skip to navigation

Threat reportRansomwareTL-2026-6191

Operation KillSwitch: Law Enforcement Takedown of KillSec (Kill Security / k1llsec) Ransomware-as-a-Service Group

highMONITORING

On 30 September 2026 a Hamburg-led international operation (Europol, Eurojust, Bitdefender, Group-IB) seized KillSec's leak site and five central servers, secured at least 110 TB of stolen data and provisionally arrested three suspects. KillSec, a financially motivated RaaS active since about 2024, used phishing, exposed RDP brute force, exploited internet-facing software and misconfigured cloud storage for double extortion. First disclosed .

Key facts

IdentifiersTL-2026-6191
Also known asOperation KillSwitch
SeverityHIGH
First disclosed
Affected productsVarious Internet-facing applications, publicly accessible/misconfigured cloud storage, exposed RDP services, VMware ESXi hosts
Weaknesses (CWE)CWE-284
AttributionKillSec (high confidence)
MalwareKillSec ESXi locker, KillSec Windows locker, killsec, killsec3, telegram
ToolsTor - S0183
MITRE ATT&CK techniquesT1110 Brute Force, T1133 External Remote Services, T1190 Exploit Public-Facing Application, T1489 Service Stop, T1490 Inhibit System Recovery, T1530 Data from Cloud Storage, T1566.002 Phishing: Spearphishing Link, T1595 Active Scanning, T1657 Financial Theft
MotivationFINANCIAL
Target sectorsfinance, health, government administration, insurance, technology, it-services
Target regionsNorth America, Asia-Pacific, Europe, Middle East and Africa, Latin America
Detection rules9 (1 shown free)
Sources9 cited sources

Detection coverage

As of 2026-11-16, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6191 across Splunk SPL, Microsoft KQL and Sigma, covering 12 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: KillSec ESXi Locker VM Shutdown, Snapshot Deletion and Log Erasure

Detects the pre-encryption behaviour of the KillSec ESXi locker announced in November 2024: powering off or killing virtual machines (T1489), deleting snapshots to inhibit recovery (T1490) and erasing or stopping logging (T1070). Searches ESXi syslog and shell logs forwarded to Splunk and alerts when a host shows two or more of the action classes, or ten or more matching events, within the search window.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1490, T1489, T1070
  • Data sources: vmware_esxi_syslog, vmw-syslog, vmware:esxlog:shell
  • Severity: high
  • Confidence: high

Splunk SPL

index=esxi (sourcetype="vmw-syslog" OR sourcetype="vmware:esxlog:shell") earliest=-24h ("snapshot.removeall" OR "snapshot.remove" OR "vmsvc/power.off" OR "vmsvc/power.shutdown" OR "esxcli vm process kill" OR "vmsyslogd stop" OR "rm -f /var/log" OR "rm -rf /var/log" OR "esxcli system syslog")
| eval action=case(match(_raw,"snapshot[.]remove"),"snapshot_deletion",match(_raw,"power[.](off|shutdown)|vm process kill"),"vm_shutdown",true(),"log_tamper")
| stats count AS events dc(action) AS distinct_actions values(action) AS actions min(_time) AS first_seen max(_time) AS last_seen BY host
| where distinct_actions>=2 OR events>=10
| eval threat="TL-2026-6191 KillSec ESXi locker VM shutdown, snapshot deletion, log erasure"
| convert ctime(first_seen) ctime(last_seen)
| table threat host events actions first_seen last_seen

Microsoft KQL

Syslog
| where TimeGenerated > ago(24h)
| where SyslogMessage matches regex '(?i)(snapshot[.]remove|vmsvc/power[.](off|shutdown)|esxcli[ ]+vm[ ]+process[ ]+kill|vmsyslogd[ ]+stop|rm[ ]+-r?f[ ]+/var/log|esxcli[ ]+system[ ]+syslog)'
| extend action = case(SyslogMessage matches regex '(?i)snapshot[.]remove', 'snapshot_deletion', SyslogMessage matches regex '(?i)(power[.](off|shutdown)|vm[ ]+process[ ]+kill)', 'vm_shutdown', 'log_tamper')
| summarize events = count(), distinct_actions = dcount(action), actions = make_set(action), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by Computer, HostIP
| where distinct_actions >= 2 or events >= 10
| project Computer, HostIP, events, actions, FirstSeen, LastSeen

Sigma

title: KillSec ESXi Locker VM Shutdown Snapshot Deletion or Log Erasure
id: 2b9d4e71-5c3a-4f86-b1d2-7a8e90c13f02
status: experimental
description: Detects ESXi shell commands that delete snapshots, power off or kill virtual machines, or stop or erase logging. This matches the documented behaviour of the KillSec ESXi locker (T1490, T1489, T1070).
references:
  - https://www.group-ib.com/media-center/press-releases/operation-killswitch-killsec/
  - https://www.bitdefender.com/en-gb/blog/businessinsights/bitdefender-supported-operation-killswitch-what-killsec-takedown-means-defenders
author: Threadlinqs Team
date: 2026/11/16
tags:
  - attack.impact
  - attack.t1490
  - attack.t1489
  - attack.defense-evasion
  - attack.t1070
logsource:
  product: esxi
  service: shell
detection:
  selection_snapshot:
    Message|contains: 'snapshot.remove'
  selection_vm:
    Message|contains:
      - 'vmsvc/power.off'
      - 'vmsvc/power.shutdown'
      - 'esxcli vm process kill'
  selection_logs:
    Message|contains:
      - 'vmsyslogd stop'
      - 'rm -f /var/log'
      - 'rm -rf /var/log'
  condition: 1 of selection_*
falsepositives:
  - Planned maintenance or decommissioning of virtual machines by virtualization administrators
  - Backup software removing snapshots through the ESXi shell
level: high

Known false positives:

  • Scheduled maintenance, VM decommissioning or template clean-up performed by administrators
  • Backup and replication products that remove snapshots through vim-cmd

Tuning notes: Forward ESXi shell.log, hostd.log and syslog to the SIEM first; without them this detection is blind. Exclude your backup service accounts and maintenance windows. Correlate with SSH logons to the host from unusual sources and with enabling of the ESXi shell or SSH service.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • KillSec Phishing Link Payload Execution From Browser or Mail Client · unlock with TL Creds
  • KillSec Windows Locker Recovery Inhibition and Event Log Clearing · unlock with TL Creds
  • KillSec Anonymous Bulk Download From Public Cloud Storage · unlock with TL Creds
  • KillSec Web Server Process Spawning Shell on Internet-Facing Host · unlock with TL Creds
  • KillSec Mass Stop of Backup, Database and Security Services · unlock with TL Creds
  • KillSec Cloud Storage Public Exposure Change · unlock with TL Creds
  • KillSec Exposed RDP Brute Force Followed by Successful Logon · unlock with TL Creds
  • KillSec Tor Leak-Site and Telegram Channel Egress From Endpoints · unlock with TL Creds

Indicators of compromise

As of 2026-11-16, Threadlinqs Intelligence tracks 12 indicators of compromise for TL-2026-6191.

Sample indicators (2 of 12)

  • Domain: ks5424y3wpr5zlug5c7i6svvxweinhbdcqcfnptkfcutrncfazzgz5id[.]onion
  • Domain: operation-killswitch[.]com

Defanged, TLP:CLEAR. Full set of 12 indicators: unlock with TL Creds.

12 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Operation KillSwitch was led by the Hamburg State Criminal Police Office and Hamburg Public Prosecutor's Office, coordinated by Europol and Eurojust, with technical support from Bitdefender (infrastructure mapping and monitoring) and Group-IB (intelligence on operations, infrastructure and key enablers). Ten countries took part: Belgium, Finland, Germany, Greece, the Netherlands, Romania, Spain, Switzerland, the United Kingdom and the United States. On 30 September 2026 investigators took control of KillSec's leak site and five central servers, redirected the group's domains to a seizure notice, and secured at least 110 TB of stolen data (the 110 TB figure comes from Group-IB and secondary reporting and should be treated as provisional). Three suspects were provisionally arrested and eight properties searched in Greece, Romania, Spain and the UK. Suspected roles include administrator/main operator (reportedly 16 years old), developer (turned 18 in August 2026), negotiator and affiliate. The US separately charged Dutch national Fouad Eltibrizi (alias 'Archduke'), arrested in the UK, who is awaiting extradition. Investigations into other members and cryptocurrency flows continue.

KillSec (also Kill Security, k1llsec) was first identified by Group-IB in 2024 as a financially motivated ransomware-as-a-service operation recruiting affiliates for a share of each ransom. The original locker was Windows-only (USD 250 entry fee, 12% ransom share); builds required administrator approval. A Tor-based affiliate platform (KillSec 2.0, analysed by Group-IB in October 2024) managed victims, negotiations and payload configuration; a KillSec 3.0 platform followed. In November 2024 the group announced an ESXi locker that shuts down virtual machines, deletes snapshots and erases logs. By January 2025 it recruited skilled pentesters (forum reputation or USD 1,000 deposit) and raised the affiliate share to 20%. Some affiliates also worked with LockBit, RansomHub, Qilin and Bashe. Group-IB lists 274 organizations on the leak site (about 35% US, 17% India; Brazil, UK, Australia and Colombia about 3% each); financial services and healthcare were most affected, plus government bodies, an insurer and IT/software providers. Encryption was not required for a listing: KillSec also sold stolen data (asking USD 5,000-500,000), and a substantial share of claimed victims involved data taken from publicly accessible, misconfigured cloud storage without network intrusion. Europol reported at least 70 suspected attacks against German organizations, including 18 in Hamburg.

Initial access per Group-IB: phishing, brute force of exposed RDP, exploitation of known vulnerabilities in internet-facing applications, and misconfigured cloud storage. Europol/Bitdefender add data theft followed by publication threats (double extortion) and reported use of AI to build and maintain infrastructure and to identify potential victims. Operation-wide figures are about 1,000 suspected attacks, about 500 identified as successful (subject to revision). No CVEs, malware hashes or IP addresses have been published. Infrastructure removal does not close the underlying exposure gaps, and affiliates may reuse the same TTPs under other ransomware brands.

MITRE ATT&CK techniques by tactic:

Credential Access

T1110 Brute Force

Initial Access

T1133 External Remote Services; T1190 Exploit Public-Facing Application; T1566.002 Phishing: Spearphishing Link

Impact

T1489 Service Stop; T1490 Inhibit System Recovery; T1657 Financial Theft

Collection

T1530 Data from Cloud Storage

Reconnaissance

T1595 Active Scanning

Remediation

Patches

  • No CVEs named in sources; apply vendor patches for all internet-facing applications and hypervisors

Immediate actions

  • Patch internet-facing software first, prioritizing vulnerabilities known to be exploited in the wild
  • Audit cloud storage access and remove public exposure, especially orphaned or forgotten buckets and shares from ended projects, acquisitions or temporary tests
  • Enforce MFA on all remote access and remove direct RDP exposure to the internet
  • Monitor leak sites and underground markets for early signs of exposure

Workarounds

  • Restrict unnecessary exposed services, ports and administrative paths; segment critical systems
  • Enforce least privilege and review privileged accounts regularly

Longer-term hardening

  • Maintain a continuous inventory of internet-facing assets including cloud storage and remote access services
  • Keep offline, immutable backups and regularly test recovery
  • Protect virtualization platforms and hypervisor management consoles as critical systems and limit administrative access
  • Centralize logging and monitor unusual data transfers, privilege changes and remote access
  • Scrutinize software and IT service providers that hold sensitive data

Affected and fixed versions

  • Various — Internet-facing applications, publicly accessible/misconfigured cloud storage, exposed RDP services, VMware ESXi hosts

Timeline

  • Group-IB analyses the Tor-based KillSec 2.0 affiliate platform used to manage victims, negotiations and payload configuration (month-level date; KillSec first identified in 2024).
  • KillSec announces an ESXi locker that shuts down VMs, deletes snapshots and erases logs (month-level date).
  • DataBreaches.net reports KillSec3 leak-site entries based on data already exposed in misconfigured storage.
  • KillSec recruits skilled pentesters (forum reputation or USD 1,000 deposit), raises affiliate share to 20% and declares hospitals off-limits (month-level date).
  • National investigations begin in early 2025 (month-level precision in sources; placeholder day).
  • Most recent KillSec leak-site posting before the takedown.
  • Operation KillSwitch: leak site and five central servers seized, domains redirected to seizure notice, at least 110 TB of data secured, three provisional arrests, eight property searches in Greece, Romania, Spain and the UK; Fouad Eltibrizi arrested in the UK per US DOJ.
  • Europol announces results; Bitdefender and Group-IB publish analyses of the operation and defender takeaways.
  • Reporting on US charges against Dutch national Fouad Eltibrizi (alias Archduke), awaiting extradition.

Sources cited

Previous and next in ransomware

Drafted by the Threadlinqs research pipeline from 9 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats