Ransomware family
Conti Ransomware Decryption & Data Recovery
- Inactive
- High
- Some versions decryptable
Conti was one of the most destructive ransomware-as-a-service operations of 2020-2022, run by Wizard Spider (the TrickBot crew), with over 1,000 victims and more than USD 150 million collected. The brand dissolved in 2022 after its internal chats and source code leaked, and its members dispersed into Black Basta, Royal, Akira and other successors.
- First seen
- 2019-12
- File extensions
- .CONTI .[5位随机大写字母] .[5位随机大小写字母数字]
- Ransom notes
- CONTI_README.txt
- Affected platforms
- Windows / Linux / VMware ESXi
Family profile
- File extensions
- .CONTI
- .[5位随机大写字母]
- .[5位随机大小写字母数字]
- .KREMLIN
- .RUSSIA
- .PUTIN
- Ransom notes
- CONTI_README.txt
- readme.txt
- R3ADM3.txt
- CONTI.txt
- Contact patterns
- A one-to-one Tor (.onion) negotiation portal linked directly from the note
- The Conti News Tor leak site and its clearnet mirror domains (all offline since 2022)
- Offshore encrypted-mail addresses listed in the note in early builds
- Bitcoin only, with a wallet generated per victim
- Post-leak derivatives use their own .onion sites or mailboxes and are unrelated to the original crew
- Aliases / versions
- Conti Ransomware、Conti v2、Conti v3、Wizard Spider(运营团伙,亦称 GOLD BLACKBURN / FIN12 / DEV-0193)、Conti News(暗网泄露站)、MeowCorp(源码泄露衍生变种)
- First seen
- 2019-12
- Status
- Inactive
- Operational status
- Operation shut down
- Threat level
- High
- Affected platforms
- Windows
- Linux
- VMware ESXi
- Tags
- Defunct
- Legacy family
- Ransomware-as-a-Service
- Double extortion
- Targets virtualization
- Phishing
- RDP brute force
- Exploits vulnerabilities
There is no free public decryptor for genuine Conti. Each file key is wrapped with a victim-specific RSA-4096 public key; the internal chats leaked on 27 February 2022 and the encryptor source and admin panel that followed in early March contained none of the operators' RSA private keys, so no real case can be reversed from them. No More Ransom still lists no Conti tool.
One exception exists: MeowCorp, a third-party build derived from the leaked source that appends .KREMLIN, .RUSSIA or .PUTIN. In early 2023 someone published 258 private keys for that variant on a Russian-language forum, and Kaspersky folded them into its free RakhniDecryptor, covering roughly 257 victims of that build. It works only for that variant and not for genuine Conti or other source-derived builds.
Separately, some low-skill copycats hardcode or leave keys on the host when compiling derivatives; those individual cases can sometimes be solved with a purpose-built tool, but only on the strength of reverse engineering an actual sample - never inferred from the extension. Any tool claiming to decrypt Conti should first prove itself on your own copies in an isolated environment.
Latest activity
A US court sentenced Ukrainian national Oleksii Lytvynenko to four years over his role in Conti; he joined in September 2021, built a loader and handled stolen data from 12 victims before his 2023 arrest in Ireland.
SourcesUkrainian national Oleksii Lytvynenko pleaded guilty in the US to wire fraud conspiracy over his Conti role; the DoJ says Conti hit over 1,000 victims worldwide and collected more than USD 150 million.
Sources
Overview
Conti was first catalogued in December 2019 and scaled through 2020. Descended from Ryuk, it was run by the Russian-speaking Wizard Spider crew - the TrickBot gang - as ransomware-as-a-service: a core team kept the encryptor, negotiation portal and Conti News leak site running while affiliates handled intrusion for a share.
The 14 May 2021 attack forced Ireland's Health Service Executive to shut down its national IT estate; only about 95 percent of servers and devices were back by September. Attacks on Costa Rican government bodies from 17 April 2022 led the country to declare a national emergency on 8 May. Joint advisory AA21-265A from CISA, the FBI and the NSA counted more than 400 attacks at first and more than 1,000 by its February 2022 update.
The turning point was 27 February 2022: after Conti publicly backed Russia, a Ukrainian researcher dumped roughly 60,694 internal chat messages from its Jabber servers, and the encryptor source code and admin panel followed days later. Washington posted rewards in May - up to USD 10 million for the leadership's identity or location and up to USD 5 million for arrests and convictions. The negotiation and admin panels went dark on 19 May and the leak and negotiation sites went offline on 23 June 2022. The FBI estimated that as of January 2022 there were over 1,000 victims and more than USD 150 million paid.
The brand died, the people did not. Research ties HelloKitty, AvosLocker, Hive, BlackCat, BlackByte and Karakurt to Conti personnel or infrastructure, and Black Basta and Royal/BlackSuit are widely held to have absorbed its crews; in July 2023 Arctic Wolf linked Akira to Conti-affiliated actors with high confidence, citing ransom-payment flows and code similarity. Enforcement continues: in May 2025 Germany's federal police named the syndicate's leader "Stern" as Vitaly Nikolaevich Kovalev, and on 11 September 2026 Ukrainian national Oleksii Lytvynenko was sentenced to four years in the US for his part in Conti attacks, having been arrested in Cork in July 2023 and pleaded guilty in June 2026. Conti now matters as a legacy: the tradecraft was inherited wholesale, the code still spawns new builds, and data encrypted in 2021-2022 still awaits a verdict.
How to identify it
Extensions. Early builds appended .CONTI; from 2021 a random five-letter uppercase string (.RHMLM, .UAKXC); from January 2022 a five-character mixed-case alphanumeric string (.ZG7Ak, .wjzPe) chosen to evade rules matching the all-uppercase pattern. An extension that looks random is therefore typical of Conti, not a reason to rule it out.
Ransom note. CONTI_README.txt, readme.txt, R3ADM3.txt or CONTI.txt are dropped in affected directories; the English text claims data theft and links to a Tor negotiation portal, with early builds also listing mail addresses. The wallpaper is normally untouched.
Derivatives. The .KREMLIN, .RUSSIA and .PUTIN extensions belong to MeowCorp, a third-party build made from the leaked source - not the original crew, yet the only strain with a public decryptor.
Bottom line. Anything labelled Conti after June 2022 is almost certainly a source-derived build or a misattributed successor; Black Basta, Royal and Akira each use different patterns. Attribution needs three to five encrypted files, the original note and the relevant logs.
Infection vectors
Conti's access playbook was copied across the whole ransomware ecosystem in 2021-2022 and still describes the most common intrusion paths:
- Phishing that delivers a loader. Malicious attachments or links drop TrickBot, BazarLoader or IcedID, which stage Cobalt Strike; from 2021 BazarLoader and BazarBackdoor progressively replaced TrickBot as the main delivery channel.
- Stolen or weak RDP credentials. Straight logon with valid credentials, no exploit needed - the CISA advisory ranks this alongside phishing as a primary vector.
- Internet-facing vulnerabilities. The ProxyShell Exchange chain (CVE-2021-34473 / 34523 / 31207, documented end to end by Sophos) and FortiGate CVE-2018-13379 and CVE-2018-13374.
- Lateral movement and escalation. Mimikatz and ProcDump against lsass, Zerologon (CVE-2020-1472) and PrintNightmare (CVE-2021-34527) for privilege, then PsExec, MS17-010 and commercial remote-access tools such as AnyDesk, Atera, Splashtop and Remote Utilities. Log4Shell (CVE-2021-44228) belongs here rather than at the perimeter: in December 2021 threat intelligence recorded Conti using it inside already-compromised networks to reach VMware vCenter.
- Exfiltration. Rclone syncing data to Mega and similar cloud storage before encryption.
In one intrusion documented by The DFIR Report, about five days elapsed between initial infection and domain-wide deployment, and the encryptor was pushed to every domain-joined host by a batch script run from the backup server. Backups first, then everything else - the signature of this lineage.
Encryption behavior
Algorithms and speed. 2020 samples showed traces of both AES-256 and a ChaCha variant, and vendors were still documenting AES-256 in early 2021; the January 2022 update is confirmed as a per-file 256-bit ChaCha key. In every build that file key is wrapped with a victim-specific RSA-4096 public key that never touches disk. With up to 32 worker threads driven by I/O completion ports, Conti ranked in the fastest tier measured - the window between noticing trouble and losing everything is often tens of minutes.
Adjustable scope. The encryptor takes command-line flags. The deployment command recorded by The DFIR Report was -m -net -size 10 -nomutex -p \\HOST\C$, where -size 10 encrypts only a proportion of each file; later builds added -safeboot and -disablesafeboot. Partial encryption depends on those flags, so never assume it - measure the actual files.
Recovery inhibition. Shadow copies are deleted via vssadmin and WMI, up to 146 security, backup, database and mail services are stopped, and the Windows Restart Manager releases locked handles so live database files can be encrypted. Builds from January 2022 could reboot into Safe Mode with networking to sidestep security software.
Lateral and virtualisation. The encryptor reaches neighbouring hosts over SMB 445 and encrypts writable shares; published research also documents a Linux variant that encrypts virtual machine files directly on VMware ESXi hosts. Data was stolen before encryption and published in stages on Conti News.
Assess before you act
Recoverability assessment
Assessing Conti recovery starts from a fact no other family shares: the crew no longer exists. The leak site went down in 2022 and the portal is dead, so there is no counterparty to pay; anyone offering Conti support or keys today is running a second fraud. We do not pay ransoms and do not negotiate - our work is technical recovery and forensics.
1) Public decryptor (one variant only). Kaspersky's RakhniDecryptor covers the derived MeowCorp build (.KREMLIN / .RUSSIA / .PUTIN) using the 258 keys published in 2023. Genuine Conti has none - leaked source code is not leaked keys.
2) Repair space from partial encryption. Where a -size style parameter was used, database files, virtual disks and mail stores may retain large untouched regions, opening the door to page-level extraction and logical rebuilds. Conti also ran full encryption often enough that the overwrite pattern must be measured first.
3) Backups, snapshots and shadow copies. Shadow copies are usually gone, but offline and offsite backups, storage and hypervisor snapshots and cloud version history still give the highest yields. Because this lineage destroyed backup systems first, verify the media are genuinely intact.
4) Unencrypted copies and log replay. Recycle bins, endpoint caches, BI staging databases, ERP archive exports and transaction logs can support reconstruction; on old cases, chase copies held by branches and partners.
5) Low-level carving. Some deployments wrote a new encrypted file and deleted the original, leaving data in unallocated clusters - which survives only if the volume was not written to since. Shelved offline disks are the most promising category here.
We commit to a verifiable assessment and a clearly bounded recovery scope.
Our response plan
Hit by Conti ransomware? What to do
Containment and forensic preservation
If encryption is still running, cut affected hosts, ESXi servers and storage paths off the network, and do not reboot or power off - the Conti toolchain commonly leaves Cobalt Strike, AnyDesk or Atera resident. Image or snapshot the domain controller, backup server and hypervisor management hosts first, export logs from edge appliances, VPN, Exchange and Active Directory, and preserve three to five encrypted files plus the original note. For dormant 2021-2022 cases the priority instead is establishing whether the original disks were written to since and whether offline media still exist.
Family identification and variant triage
Use the extension pattern, note structure, file trailer markers and sample reverse engineering to decide whether this is genuine Conti, a source-derived build such as MeowCorp, or a successor family (Black Basta, Royal, Akira) mislabelled as Conti - the three lead to entirely different recovery paths. In parallel, confirm the algorithm (AES-256 or ChaCha20) and the deployment parameters, and check for the hardcoded or locally retained keys typical of low-skill builds.
Recoverability assessment and plan sign-off
In an isolated environment, measure the real overwrite pattern (full versus proportional) and run sample repairs on the critical databases and virtual disks; where MeowCorp is confirmed, validate RakhniDecryptor against genuine samples. In parallel, inventory backups, storage snapshots, hypervisor snapshots and unencrypted copies, and verify whether the backup media were tampered with. Deliver a written assessment naming which systems go the decryption route, which need page-level database rebuilds and which rely on backup rollback or carving, with expected recovery ranges, timelines and a business restoration order - then execute only after sign-off.
Recovery execution and data disposition
All work happens on images or copies with originals kept read-only. Restore in business priority order: domain controllers and identity first, then core databases such as ERP and MES, then file and mail systems. For ESXi, repair virtual disk structures and mount them to extract inner data rather than overwriting the original datastores. After each batch run integrity checks and business-side verification - reconciliation, report comparison, application start-up tests. Assess the exfiltration impact in parallel: the Conti leak site is gone, but data published back then may still circulate on mirrors and in intelligence communities, which drives notification duties and the scope of credential rotation.
Attribution, hardening and handover
Reconstruct the full kill chain: whether entry came from a phishing loader, stolen RDP credentials or an unpatched Exchange or FortiGate flaw, where domain administrator credentials leaked, and when the backup system was taken out. Remove remote-access tooling, rogue accounts, scheduled tasks and GPO backdoors; reset credentials domain-wide and enforce MFA on VPN and RDP; segment the ESXi management network and close external SSH; patch edge appliances; rebuild backups to a 3-2-1 design with immutable copies. Close with an incident report and a formal handover. Because Conti's tradecraft was inherited wholesale by its successors, the same hardening defends against Black Basta and Akira.
Risk warning
What not to do
- Do not trust anyone claiming to be Conti support or offering to buy keys on your behalf. The crew dissolved in 2022 and its negotiation portal is long dead; treat every such contact as a second fraud.
- Do not run downloaded Conti decryptors against original disks. Apart from Kaspersky's RakhniDecryptor for the MeowCorp variant, most are fakes or malware droppers - any trial must run on copies.
- Do not reboot or power off hosts and ESXi servers while encryption is running, and do not repurpose or reinstall shelved victim disks just because the incident is old; that destroys the carving option outright.
- Do not delete the ransom notes (CONTI_README.txt, readme.txt and the rest) or the encrypted samples, and do not rush to clean up the malware files - they are the only basis for telling genuine Conti, a derivative and a successor family apart.
- Do not reconnect backup servers, tapes or portable drives to the network before confirming the media are intact; launching domain-wide deployment from the backup server was standard practice for this lineage.
- Do not attribute an incident to Conti from a random extension alone. Most cases after June 2022 are source-derived builds or successors such as Black Basta and Akira, and a wrong call leads straight to the wrong recovery plan.
Emergency response
Data already encrypted? Stop and let an engineer look first
We do not pay ransoms and we do not negotiate with attackers. Engineers run a free assessment first, then propose a recovery plan and a firm quote.
Related scenarios
Domain Controller Compromise and Estate-Wide Encryption
A compromised domain controller hands the attacker a legitimate administrator identity, allowing an encryptor to be pushed to every host at once through Group Policy or remote execution. This page covers how such incidents present, the correct order for Active Directory recovery, and how to decide between cleanup and full rebuild.
ESXi / Hyper-V Virtualization Encrypted by Ransomware
Hypervisor-level encryption causes the widest blast radius of any ransomware event: dozens of production VMs go dark within an hour or two. This page covers what Linux ESXi encryptors actually do — shut down guests, encrypt vmdk, delete snapshots — the recovery value of flat disk files, and how Hyper-V and Proxmox cases differ.
Backups Deleted or Destroyed
Modern ransomware follows a fixed sequence: destroy the backups, then encrypt the data — deleting shadow copies, encrypting repositories, disabling jobs, and exploiting backup software flaws to steal credentials. This page covers what can still be inventoried once backups fail, why replication propagates encrypted files off-site, and what offline and immutable copies are really worth.
Database Encrypted by Ransomware
When database files are encrypted, every business system that depends on them stops at once. This page explains how we triage an encrypted database, how recoverability is assessed, and when file repair, backup-plus-log restore, or rebuild is the right path.
Related industries
Healthcare Ransomware Response and Recovery
When a hospital is hit, registration, consultation, orders, billing, laboratory and imaging fail at the same moment and care falls back to paper. This page covers the healthcare threat picture, a recovery priority built around clinical continuity, and the handling of patient data and compliance obligations.
Manufacturing Ransomware Response and Recovery
Ransomware in manufacturing hits information systems and production cadence at the same time: with ERP down there are no orders, with MES down there is no schedule, and an encrypted drawing library takes the process documentation for an entire product line with it. This page covers the asset profile, recovery priorities and targeted defences.
Government and Public Sector Ransomware Response
Public sector ransomware incidents run on three lines at once: service interruption, data security and mandatory reporting. When document circulation, archives and integrated service platforms stop, both public services and internal operations are affected. This page covers the handling sequence, reporting duties and hardening priorities.
Similar families
- Some versions decryptable
Black Basta
Black Basta was a Conti-derived RaaS operation that emerged in April 2022 and affected more than 500 organisations, known for QakBot delivery and Microsoft Teams IT-impersonation social engineering. It disbanded in February 2025 after its internal chat logs leaked, though its tradecraft carried over to successors such as Cactus.
- Some versions decryptable
Akira
Akira is a ransomware-as-a-service operation that emerged in March 2023, breaking in through VPNs without MFA and edge-device flaws, then encrypting Windows estates and VMware ESXi clusters under double extortion. CISA's November 2025 advisory update calls it an imminent threat to critical infrastructure.
- Some versions decryptable
LockBit
LockBit is one of the largest ransomware-as-a-service operations in the world. Despite the 2024 law-enforcement takedown it returned as LockBit 5.0, with working Windows, Linux and VMware ESXi payloads, and it remains one of the most frequently seen families in China.
FAQ
Conti Frequently asked questions
Can files with the .CONTI extension still be decrypted?
Genuine Conti has no public decryptor. File keys are wrapped with a victim-specific RSA-4096 key, and the 2022 leak exposed the encryptor source rather than any private key, so no general decryption route exists. The one exception is the derived MeowCorp build (.KREMLIN / .RUSSIA / .PUTIN), where Kaspersky's RakhniDecryptor covers some victims using the 258 keys that were published. Real recovery therefore runs through backups, snapshots, database repair where encryption was partial, and carving - all of which need a sample-level assessment first.
Conti shut down years ago - why am I being hit by it now?
It is usually one of three things. The source code leaked in March 2022 was rebuilt by third parties and redeployed, sometimes still carrying Conti artefacts. The real actor is a successor crew - Black Basta, Royal/BlackSuit, Akira - and a detection rule inherited the old family name. Or someone is simply borrowing the brand for pressure. Recoverability differs sharply between the three, so the case must be triaged from samples rather than from the name.
The source code leaked - why can't a decryptor be written from it?
Because the leak contains the encryption side, not the RSA private keys the operators held. The source lets researchers read the algorithm and the key-wrapping routine and confirm there is no exploitable flaw in it; without the private key the ChaCha20 or AES file keys cannot be recovered. The cases that do get solved involve low-skill copycats who hardcoded a key when compiling a derivative or left key material on the victim host - each of which has to be confirmed by reverse engineering that specific sample.
We shelved disks encrypted back in 2022 - is that data still recoverable?
It is worth assessing, and shelving the disks actually helps. The keys remain with the attackers, but decryption is not the only route: if the deployment used proportional encryption, databases and virtual disks may retain large intact regions; offline backups, offsite tapes and historical copies held by branches or partners often still exist; and because the original volumes were never written to again, carving succeeds more often than on fresh cases. Start with a read-only assessment that leaves the originals untouched, then decide on the investment.
How should ESXi virtual machines encrypted by Conti be handled?
Published research documents a Conti Linux variant that encrypts vmdk, vmx and related files directly on ESXi hosts, so one compromised hypervisor takes down every workload on it. The essentials: do not reinitialise the datastore and do not create new VMs on it. Image the datastore whole, then work on the copy - repair the virtual disk partition table and filesystem structures, mount them and extract the inner data. In parallel, check storage-layer snapshots, VM-level copies in the backup software and any replication targets. Before restoring, confirm the management network is segmented and SSH is disabled so nothing gets encrypted twice.
Sources
- Conti Ransomware (Alert AA21-265A) - CISA
- Conti (S0575) - MITRE ATT&CK
- Conti Ransomware Attacks Persist With an Updated Version Despite Leaks - Zscaler ThreatLabz
- Continuing the Bazar Ransomware Story - The DFIR Report
- Conti-based ransomware 'MeowCorp' gets free decryptor - BleepingComputer
- TAU Threat Discovery: Conti Ransomware - VMware Carbon Black
- Conti affiliates use ProxyShell Exchange exploit in ransomware attacks - Sophos
- Conti and Akira: Chained Together - Arctic Wolf
- Conti ransomware finally shuts down data leak, negotiation sites - BleepingComputer
- Ukrainian hacker gets four years in US prison over Conti ransomware attacks - The Record
- Conti (win.conti) - Malpedia
- Ransom.Conti detection page - Malwarebytes
External links are provided for reference only. The content is published by third parties and does not represent our position.
Updated