Threat Summary
A newly published OTX pulse exposes the internal tooling of The Gentlemen, a ransomware operation targeting U.S. organizations in the defense, healthcare, technology, and aerospace sectors. Analysis of seized/observed server infrastructure revealed a fully operational TukTuk C2 framework (version 2.0) — a cross-platform command-and-control stack shipping both Windows and Linux agents, a backend infrastructure layer, and a web-based management panel for operators.
The same server contained eb.sys, a kernel driver matching the GentleKiller payload, alongside a family of EDR-neutralization tools tracked as EDRKiller, WarsawKiller, and UnknownKiller. Most alarming: the infrastructure hosted structured training materials organized into four progressive lessons on BYOVD (Bring Your Own Vulnerable Driver) techniques and vulnerable driver abuse — indicating The Gentlemen is industrializing EDR-killing tradecraft and onboarding affiliates with standardized playbooks, not just deploying one-off tooling.
Tagging on the pulse references Greenshot (a legitimate screenshot utility likely abused for reconnaissance/screen capture) and Jira exfiltration — pointing to a double-extortion model where victim data is staged and exfiltrated through legitimate collaboration platforms before encryption. The attack chain is best modeled as: initial access → TukTuk agent deployment → GentleKiller/EDRKiller driver load to blind endpoint security → credential and data harvesting → Jira-based exfiltration → ransomware detonation.
Threat Actor & Malware Profile
The Gentlemen (Ransomware Operation)
- Target profile: United States — defense industrial base, healthcare, technology, aerospace. Sector selection suggests both financial extortion and potential intelligence-adjacent collection value.
- Operational maturity: Versioned C2 framework (TukTuk 2.0), modular killer tooling, and formalized operator training indicate a mature, scalable RaaS-style operation.
TukTuk C2 Framework v2.0
- Distribution: Deployed post-compromise as the primary implant; cross-platform agents (Windows/Linux) suggest targeting of heterogeneous enterprise estates including server infrastructure.
- Payload behavior: Modular agent architecture with tasking from a centralized management panel; supports operator-driven hands-on-keyboard activity typical of ransomware precursors.
- C2 communication: Resolves attacker-controlled infrastructure; the domain
borjumaniya.storeis identified in this pulse as associated infrastructure (T1071.001, T1568). - Persistence: Service- and agent-based persistence consistent with long-dwell pre-ransomware staging (T1543.003).
GentleKiller / EDRKiller / WarsawKiller / UnknownKiller
- Function: EDR/AV neutralization. The
eb.sysdriver (GentleKiller) is loaded into the kernel to terminate or blind security products from ring 0 (T1562.001 — Impair Defenses). - Anti-analysis / delivery technique: BYOVD — a legitimately signed but vulnerable driver is dropped and loaded, then exploited to gain kernel-level control and kill protected security processes (T1068). Kernel payloads bypass most user-mode hooks, making them invisible to standard EDR telemetry.
- Detection implication: User-mode process events will not show the kill. Defenders must monitor driver load events, service creation for
.sysbinaries, and Defender tampering artifacts instead.
IOC Analysis
The pulse carries 11 indicators; the exposed sample includes:
- 1 domain —
borjumaniya.store: TukTuk-associated C2/staging infrastructure. Operationalize via DNS sinkhole, proxy block, and retro-hunt of DNS logs. Newly registered.storeTLD infrastructure is high-signal — legitimate business traffic to this namespace is near zero. - 1 MD5 / 2 SHA1 / 4 SHA256 file hashes — TukTuk agents and killer tooling samples. SHA256 values should go directly into EDR block-by-hash policies; MD5/SHA1 remain useful for legacy tooling and sandbox pivots.
Operationalization guidance:
- Ingest via OTX DirectConnect / API into your TIP (MISP, OpenCTI) and push to Sentinel watchlists or Defender custom indicators with
Blockaction. - Hash-match retro-hunts across
DeviceFileEventsand email/web gateways for the last 30–90 days — BYOVD ransomware precursors typically dwell before detonation. - Note the pulse sample is truncated (8 of 11 indicators shown); pull the full indicator set from the OTX pulse endpoint before scoping your hunt.
Detection Engineering
---
title: The Gentlemen BYOVD EDR Killer Driver Load
id: 9f1c2a34-7b5d-4e6a-9c01-2d4e5f6a7b8c
status: experimental
description: Detects kernel driver loads associated with The Gentlemen ransomware EDR-neutralization tooling (GentleKiller eb.sys) via known IOC hashes and driver filename. Kernel payloads bypass user-mode EDR hooks, making driver_load telemetry the primary detection surface.
author: Security Arsenal Threat Intelligence
date: 2026/09/04
modified: 2026/09/04
references:
- https://oasis-security.io/blog/The-Gentlemen-Ransomware-Hacker-Groups-TukTuk-Framework
logsource:
product: windows
category: driver_load
detection:
selection_name:
ImageLoaded|endswith:
- '\eb.sys'
selection_hash:
Hashes|contains:
- '97BD65E98CDC4E93D49EDD4EA905D43A61244DF0FD3323E6649330DE3B1BE091'
- 'E2B31AC7EE077B26332444A83A68AB75BE641113E7D86979D844A0F3478F01F9'
- 'E74088419DE2E5B47B1889F2BA1369CB4B436405CE03CF07DA452791681F9923'
- '096EC37870EB401793592C9B53B5B52FC7A70B113BC2D9CD3F53231142D6C584'
condition: 1 of selection_*
falsepositives:
- Unknown. eb.sys is not a standard Microsoft driver name.
level: critical
tags:
- attack.defense_evasion
- attack.t1562.001
- attack.t1068
---
title: EDR Killer Kernel Driver Service Creation
id: 3a7b9d12-4c5e-4f8a-b2d3-6e7f8a9b0c1d
status: experimental
description: Detects creation of a Windows service pointing at a .sys kernel driver, the delivery mechanism used to stage GentleKiller/EDRKiller/WarsawKiller BYOVD payloads before EDR neutralization and ransomware execution.
author: Security Arsenal Threat Intelligence
date: 2026/09/04
modified: 2026/09/04
logsource:
product: windows
category: process_creation
detection:
selection_sc:
Image|endswith: '\sc.exe'
CommandLine|contains|all:
- 'create'
- 'binPath'
selection_driver:
CommandLine|contains:
- '.sys'
- 'type= kernel'
condition: all of selection_*
falsepositives:
- Legitimate software or hardware driver installations. Baseline against software deployment tooling and alert on non-standard parent processes.
level: high
tags:
- attack.persistence
- attack.t1543.003
- attack.defense_evasion
- attack.t1562.001
---
title: TukTuk C2 Framework DNS Resolution
id: 5c2e8f41-9a3b-4d6c-8e1f-7a2b3c4d5e6f
status: experimental
description: Detects DNS resolution of TukTuk C2 framework infrastructure associated with The Gentlemen ransomware operation. Any hit warrants immediate host isolation and memory acquisition.
author: Security Arsenal Threat Intelligence
date: 2026/09/04
modified: 2026/09/04
logsource:
category: dns
detection:
selection:
QueryName|contains:
- 'borjumaniya.store'
condition: selection
falsepositives:
- Security researcher or sandbox traffic pivoting on published indicators.
level: critical
tags:
- attack.command_and_control
- attack.t1071.001
- attack.t1568
// The Gentlemen / TukTuk C2 — unified indicator + behavior hunt
let TukTukHashes = dynamic(["4e5136230ec590ce6ef038aac6e72cb2","ba914fe77b177b45799403b16dd14765c510a074","97bd65e98cdc4e93d49edd4ea905d43a61244df0fd3323e6649330de3b1be091","138c41085f5f07adbdeff4df97a6a80252571e28","e2b31ac7ee077b26332444a83a68ab75be641113e7d86979d844a0f3478f01f9","e74088419de2e5b47b1889f2ba1369cb4b436405ce03cf07da452791681f9923","096ec37870eb401793592c9b53b5b52fc7a70b113bc2d9cd3f53231142d6c584"]);
union isfuzzy=true
(DeviceNetworkEvents
| where RemoteUrl has "borjumaniya.store"
| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessId, RemoteUrl, RemoteIP, RemotePort, ActionType),
(DeviceProcessEvents
| where ProcessCommandLine has_any ("eb.sys", "gentlekiller", "warsawkiller", "tuktuk")
or (ProcessCommandLine has_all ("sc.exe", "create", "binPath") and ProcessCommandLine has ".sys")
or (FileName =~ "bcdedit.exe" and ProcessCommandLine has_any ("testsigning", "nointegritychecks"))
| project TimeGenerated, DeviceName, FileName, ProcessCommandLine, AccountName, InitiatingProcessFileName),
(DeviceFileEvents
| where SHA256 in~ (TukTukHashes) or SHA1 in~ (TukTukHashes) or MD5 in~ (TukTukHashes)
or FileName =~ "eb.sys"
| project TimeGenerated, DeviceName, FileName, FolderPath, SHA256, InitiatingProcessFileName),
(DeviceEvents
| where ActionType == "DriverLoad" or AdditionalFields has "eb.sys"
| where AdditionalFields has_any ("eb.sys", "\\Temp\\", "\\ProgramData\\")
| project TimeGenerated, DeviceName, ActionType, FileName, FolderPath, AdditionalFields)
| order by TimeGenerated desc
# The Gentlemen / TukTuk C2 — endpoint IOC & tamper hunt
$ErrorActionPreference = 'SilentlyContinue'
Write-Host "[*] The Gentlemen / TukTuk C2 Host Hunt" -ForegroundColor Cyan
# 1. IOC hash sweep of common staging paths
$iocs = @(
'4e5136230ec590ce6ef038aac6e72cb2',
'ba914fe77b177b45799403b16dd14765c510a074',
'97bd65e98cdc4e93d49edd4ea905d43a61244df0fd3323e6649330de3b1be091',
'138c41085f5f07adbdeff4df97a6a80252571e28',
'e2b31ac7ee077b26332444a83a68ab75be641113e7d86979d844a0f3478f01f9',
'e74088419de2e5b47b1889f2ba1369cb4b436405ce03cf07da452791681f9923',
'096ec37870eb401793592c9b53b5b52fc7a70b113bc2d9cd3f53231142d6c584'
)
Write-Host "`n[1] Sweeping staging paths for IOC hashes..."
$paths = @("$env:TEMP", "$env:ProgramData", "C:\Windows\Temp", "C:\Users\Public")
foreach ($p in $paths) {
Get-ChildItem -Path $p -Recurse -File | ForEach-Object {
$h = (Get-FileHash -Algorithm SHA256 -Path $_.FullName).Hash.ToLower()
if ($iocs -contains $h) { Write-Host "[!] HASH MATCH: $($_.FullName)" -ForegroundColor Red }
}
}
# 2. Loaded killer drivers (GentleKiller eb.sys / BYOVD)
Write-Host "`n[2] Checking loaded drivers for killer tooling..."
Get-CimInstance Win32_SystemDriver | Where-Object { $_.PathName -match 'eb\.sys|gentle|warsaw|tuktuk' } |
ForEach-Object { Write-Host "[!] SUSPICIOUS DRIVER: $($_.Name) -> $($_.PathName)" -ForegroundColor Red }
# 3. Registered kernel services pointing at malicious .sys files
Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Services\*' |
Where-Object { $_.ImagePath -match 'eb\.sys|gentle|warsaw|tuktuk' } |
ForEach-Object { Write-Host "[!] SUSPICIOUS SERVICE: $($_.PSChildName) -> $($_.ImagePath)" -ForegroundColor Red }
# 4. TukTuk C2 beacons
Write-Host "`n[3] Checking DNS cache and live sessions for C2..."
Get-DnsClientCache | Where-Object { $_.Entry -match 'borjumaniya\.store' } | Format-Table
Get-NetTCPConnection -State Established | ForEach-Object {
$r = Resolve-DnsName $_.RemoteAddress
if ($r.NameHost -match 'borjumaniya') {
Write-Host "[!] LIVE C2 SESSION: $($_.RemoteAddress):$($_.RemotePort) PID $($_.OwningProcess)" -ForegroundColor Red
}
}
# 5. EDR tampering artifacts left behind by killer tooling
Write-Host "`n[4] Checking Defender tampering state..."
$pref = Get-MpPreference
if ($pref.DisableRealtimeMonitoring) { Write-Host "[!] Real-time protection DISABLED" -ForegroundColor Red }
$pref.ExclusionPath | ForEach-Object { Write-Host "[!] Suspicious exclusion: $_" -ForegroundColor Yellow }
Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows Defender' |
Where-Object { $_.DisableAntiSpyware -eq 1 } |
ForEach-Object { Write-Host "[!] Defender disabled via policy" -ForegroundColor Red }
Write-Host "`n[*] Hunt complete."
Response Priorities
Immediate (0–4 hours)
- Block
borjumaniya.storeat DNS, proxy, and EDR network protection layers; push all SHA256 indicators to block-by-hash policies fleet-wide. - Hunt for
eb.sysdriver loads and kernel-type service creation via the Sigma/KQL above. Any hit = host isolation + memory acquisition before reboot (BYOVD artifacts live in kernel space; volatile evidence is lost on restart). - Sweep Temp/ProgramData/Public staging paths with the PowerShell hunt script across internet-facing and file-server assets first.
24 Hours
- If any host shows TukTuk or EDR-killer artifacts, assume credential compromise: reset all credentials used interactively or by services on affected hosts (LSASS dumping routinely precedes ransomware staging).
- Audit Jira and collaboration-platform egress — the pulse explicitly tags Jira exfiltration. Review API tokens, service accounts, and anomalous bulk-export or attachment-download activity.
- Validate Defender Tamper Protection state fleet-wide and investigate any exclusions or disablement events in the last 30 days.
1 Week
- Enable the Microsoft Vulnerable Driver Blocklist and enforce HVCI/Kernel-mode Hardware-enforced Stack Protection where hardware supports it; deploy WDAC policies restricting driver loads to known-good signers.
- Restrict driver installation rights to a hardened admin tier; alert on any non-standard parent process spawning driver service creation.
- Deploy all three Sigma rules and the Sentinel analytic to production; run a tabletop exercise modeling a BYOVD EDR-blind scenario — your IR runbooks must assume endpoint telemetry will go dark mid-incident.
Related Resources
Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.