Back to Intelligence

Conti Ransomware Developer Sentenced to 4 Years: Detection and Hardening Guide Against Conti-Tradecraft Successors

SA
Security Arsenal Team
September 13, 2026
8 min read

Oleksii Oleksiyovych Lytvynenko, a Ukrainian national who developed encryption components for the Conti ransomware operation, has been sentenced to four years in U.S. federal prison. Lytvynenko was arrested in Ireland in 2023 and subsequently extradited to the United States to face charges related to his role in one of the most destructive ransomware-as-a-service (RaaS) operations ever documented.

For defenders, the sentencing is a milestone — but it is not a finish line. Conti formally dissolved in 2022, yet its source code leaked publicly, its operators dispersed into successor groups (Black Basta, BlackByte, Akira, Royal, and others), and its tradecraft — double extortion, rapid encryption, aggressive lateral movement via Cobalt Strike and PsExec — remains the operational template for most ransomware intrusions we respond to today. The conviction removes one developer. It does nothing to remove the playbook.

If your detection engineering still treats "Conti" as a historical artifact, you are exposed to the same TTPs wearing new branding.

Technical Analysis: The Conti Tradecraft That Still Matters

Who Was Conti, and Why Does the Code Still Matter?

Conti operated as a RaaS platform from 2020 through mid-2022, generating hundreds of millions in ransom payments and hitting hospitals, municipalities, and critical infrastructure. Two events made Conti uniquely dangerous long after its dissolution:

  1. The 2022 source code leak. A Ukrainian researcher leaked Conti's encryptor source code, internal chats, and operational playbooks after the group publicly sided with Russia's invasion of Ukraine. Multiple successor families have since been built directly on that leaked codebase.
  2. Operator migration. Conti affiliates and developers did not retire — they joined or founded Black Basta, Akira, Royal, BlackSuit, and other active operations. Lytvynenko's role as an encryption developer means the cryptographic implementation he helped build is likely still in circulation in derivative encryptors.

The Conti Attack Chain (Defender's View)

The intrusion chain Conti popularized — and that successor groups still execute — follows a predictable, detectable sequence:

  • Initial access: Phishing with TrickBot/BazarLoader/Qakbot-style loaders, or exploitation of exposed remote services.
  • Execution & C2: Cobalt Strike beacons, often delivered via DLL sideloading or reflective injection; PowerShell download cradles and encoded commands.
  • Defense evasion: Mass service termination and VSS shadow copy deletion via vssadmin delete shadows, bcdedit recovery disabling, and wmic shadowcopy delete.
  • Lateral movement: PsExec-style remote service creation, SMB-based tool staging in ADMIN$ shares, and RDP.
  • Impact: The Conti encryptor used multi-threaded AES-256 file encryption with per-file keys wrapped in RSA-4096, plus a hardcoded kill list of processes and services (databases, backup agents, hypervisors) to force file handles closed before encryption.

Exploitation Status

This news item does not describe a new vulnerability or CVE — no CVE is associated with the sentencing. The threat relevance is active and ongoing: Conti-derived encryptors and Conti-style TTPs are confirmed in-the-wild daily across successor RaaS operations. The defensive value here is detection coverage for a well-documented, still-active tradecraft.

Detection & Response

The detections below target the behaviors Conti popularized and that its successors continue to execute. They are tuned for high-fidelity alerting — not broad noise.

Sigma Rules

YAML
---
title: Ransomware Shadow Copy Deletion via Vssadmin or WMIC
id: 3f8c2a91-7e4d-4b6a-9c12-8d5e6f7a8b9c
status: experimental
description: Detects deletion of Volume Shadow Copies, a hallmark anti-recovery behavior used by Conti and successor ransomware families before encryption.
references:
  - https://attack.mitre.org/techniques/T1490/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1490
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\vssadmin.exe'
      - '\wmic.exe'
      - '\diskshadow.exe'
  selection_cli:
    CommandLine|contains:
      - 'delete shadows'
      - 'shadowcopy delete'
      - 'resize shadowstorage'
      - 'delete shadows /all'
  condition: selection_img and selection_cli
falsepositives:
  - Legitimate storage administrators resizing shadow storage (rare on servers, investigate anyway)
level: high
---
title: Ransomware Recovery Disable via Bcdedit
id: 6b1e4d72-3a9f-4c58-b2d7-9e8f1a2c3d4e
status: experimental
description: Detects bcdedit commands disabling Windows recovery mode and ignoring boot failures, consistent with Conti and successor ransomware pre-encryption staging.
references:
  - https://attack.mitre.org/techniques/T1490/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1490
  - attack.defense_evasion
  - attack.t1562
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|endswith: '\bcdedit.exe'
    CommandLine|contains:
      - 'recoveryenabled no'
      - 'bootstatuspolicy ignoreallfailures'
  condition: selection
falsepositives:
  - Rare; legitimate use is almost exclusively scripted IT provisioning
level: high
---
title: Mass Service Stop Prior to Ransomware Encryption
id: 9d2c7f45-1b8e-4a36-c5d9-4f6a7b8c9d0e
status: experimental
description: Detects net.exe or sc.exe being used to stop database, backup, or security services, matching Conti encryptor kill-list behavior executed via command line.
references:
  - https://attack.mitre.org/techniques/T1489/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1489
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\net.exe'
      - '\net1.exe'
      - '\sc.exe'
  selection_action:
    CommandLine|contains:
      - 'stop'
      - 'delete'
  selection_targets:
    CommandLine|contains:
      - 'veeam'
      - 'backup'
      - 'sql'
      - 'mssql'
      - 'exchange'
      - 'sophos'
      - 'defender'
      - 'vss'
      - 'mepocs'
      - 'memtas'
  condition: selection_img and selection_action and selection_targets
falsepositives:
  - Legitimate service administration; tune by known admin accounts and maintenance windows
level: high

KQL — Microsoft Sentinel / Defender

KQL — Microsoft Sentinel / Defender
// Hunt for Conti-style pre-encryption staging: shadow deletion, recovery disable, and service kill-list execution
// Correlate multiple anti-recovery events per device within a short window — single events may be admin noise
let AntiRecovery = dynamic(["delete shadows", "shadowcopy delete", "recoveryenabled no", "bootstatuspolicy ignoreallfailures", "resize shadowstorage"]);
DeviceProcessEvents
| where TimeGenerated > ago(24h)
| where FileName in~ ("vssadmin.exe", "bcdedit.exe", "wmic.exe", "diskshadow.exe", "net.exe", "net1.exe", "sc.exe")
| where ProcessCommandLine has_any (AntiRecovery)
   or (FileName in~ ("net.exe", "net1.exe", "sc.exe") and ProcessCommandLine has "stop" and ProcessCommandLine has_any ("veeam", "sql", "backup", "vss", "sophos"))
| summarize AntiRecoveryEvents = count(), Commands = make_set(ProcessCommandLine), Accounts = make_set(AccountName)
  by DeviceName, bin(TimeGenerated, 10m)
| where AntiRecoveryEvents >= 2
| sort by TimeGenerated desc
KQL — Microsoft Sentinel / Defender
// Sentinel Syslog/CEF variant for environments forwarding Windows events via agents
let AntiRecovery = dynamic(["delete shadows", "shadowcopy delete", "recoveryenabled no", "ignoreallfailures"]);
union SecurityEvent, CommonSecurityLog, Syslog
| where TimeGenerated > ago(24h)
| where CommandLine has_any (AntiRecovery)
| project TimeGenerated, Computer, Account, CommandLine, Process
| sort by TimeGenerated desc

Velociraptor VQL

VQL — Velociraptor
-- Hunt for evidence of shadow copy deletion and recovery tampering across the fleet
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(delete shadows|shadowcopy delete|recoveryenabled no|ignoreallfailures|resize shadowstorage)'
   OR (Name =~ '(?i)(net|sc)\.exe' AND CommandLine =~ '(?i)stop' AND CommandLine =~ '(?i)(veeam|sql|backup|vss|sophos|defender)')
VQL — Velociraptor
-- Sweep for recently dropped ransom notes in common user directories
SELECT FullPath, Size, Mtime
FROM glob(globs='C:/Users/*/Desktop/**/*readme*.txt', accessor='ntfs')
WHERE Mtime > now() - 86400

Remediation & Verification Script

PowerShell
# Conti-tradecraft hardening verification - run elevated
# 1. Confirm VSS protection: ensure shadow copies exist and deletion would be audited
Write-Host "[*] Checking Volume Shadow Copy status..." -ForegroundColor Cyan
$shadows = Get-WmiObject Win32_ShadowCopy -ErrorAction SilentlyContinue
if ($shadows) { Write-Host "[+] $($shadows.Count) shadow copies present" } else { Write-Host "[-] WARNING: No shadow copies found" -ForegroundColor Red }

# 2. Verify recovery environment is enabled (ransomware disables this via bcdedit)
$bcd = bcdedit /enum {current} | Out-String
if ($bcd -match "recoveryenabled\s+No") { Write-Host "[-] WARNING: Recovery disabled - re-enable with: bcdedit /set {current} recoveryenabled yes" -ForegroundColor Red } else { Write-Host "[+] Recovery environment enabled" }

# 3. Confirm tamper protection / critical services are running
$critical = @("WinDefend", "VSS", "VeeamBackupSvc", "MSSQLSERVER")
foreach ($svc in $critical) {
    $s = Get-Service -Name $svc -ErrorAction SilentlyContinue
    if ($s -and $s.Status -eq 'Running') { Write-Host "[+] $svc running" } elseif ($s) { Write-Host "[-] $svc is $($s.Status)" -ForegroundColor Yellow }
}

# 4. Enable process command-line auditing (required for the Sigma/KQL detections above)
$audit = auditpol /get /subcategory:"Process Creation" | Out-String
Write-Host "[*] Process Creation auditing: $audit"
$cmdLine = Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit" -Name ProcessCreationIncludeCmdLine_Enabled -ErrorAction SilentlyContinue
if ($cmdLine.ProcessCreationIncludeCmdLine_Enabled -ne 1) {
    Set-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit" -Name ProcessCreationIncludeCmdLine_Enabled -Value 1
    Write-Host "[+] Enabled command-line inclusion in process creation events"
}

# 5. Restrict PsExec-style lateral movement: verify ADMIN$ remote staging is monitored
Write-Host "[*] Recommendation: deploy attack surface reduction rule 'Block process creations originating from PSExec and WMI commands' (ASR rule d1e49aac-8f56-4280-b9ba-993a6d77406c)"

Remediation: What Your Team Should Do This Quarter

  1. Validate anti-recovery detection coverage. Shadow copy deletion and bcdedit recovery tampering are near-universal ransomware precursors and among the highest-fidelity early warnings available. Deploy the rules above and test them in a lab.
  2. Harden backup infrastructure against the Conti kill-list model. Ensure backups are immutable (object lock / WORM), credentials are vaulted and separated from domain credentials, and backup agents are excluded from standard admin tooling access.
  3. Constrain lateral movement. Block workstation-to-workstation SMB where feasible, deploy the ASR rule for PSExec/WMI child processes, and tier administrative accounts so a single compromised workstation cannot reach server infrastructure.
  4. Monitor for successor-family IOCs, not "Conti" IOCs. Subscribe to CISA and vendor intelligence on Black Basta, Akira, Royal, and BlackSuit — the encryptor names change, the staging behaviors do not.
  5. Rehearse the IR plan. The Conti model moved from initial access to domain-wide encryption in days. Your containment decision (isolate, disable accounts, sever VPN) must be executable within hours, not after a change-control meeting.
  6. Track law-enforcement outcomes as threat intelligence. Every arrest and extradition like Lytvynenko's disrupts developer talent pipelines and generates court records that expose internal tooling details — a genuinely useful source of detection insight.

The four-year sentence is a win for international law enforcement cooperation, particularly the Ireland-to-U.S. extradition pipeline. But the code Lytvynenko helped write is still encrypting networks in 2026. Defense-in-depth against the tradecraft — not the brand name — is the only posture that holds.

Related Resources

Security Arsenal Incident Response Services AlertMonitor Platform Book a SOC Assessment incident-response Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.