lockbit3.0
From extortion.wiki, the ransomware negotiation research archive
Negotiation records classified under lockbit3.0 in the current Ransomchats snapshot. This page indexes the source label; it does not independently verify attribution.
Classification follows the source dataset. Metadata is useful. It is not testimony.
Actor lineage
Global lineage directoryOverview
LockBit evolved through multiple named variants and an affiliate-based RaaS program. Operation Cronos disrupted core infrastructure in February 2024; later activity must not be read as proof that every historical affiliate remained connected.
Documentary media

2 additional reviewed records


Known aliases
| Alias | Type | First observed | Last observed | Confidence | Sources |
|---|---|---|---|---|---|
| lockbit3.0Original Ransomchats collection label retained for historical record identity. | Alternate name | Date not established | Date not established | Confirmed | Casualtek · CISA, FBI, MS-ISAC, and international partners |
| LockBit 2.0CISA evolution-table name for the second major LockBit variant; it does not identify every affiliate as the same person or crew. | Malware name | June 2021 | Date not established | Confirmed | CISA, FBI, MS-ISAC, and international partners |
| LockBit RedAlternate name for LockBit 2.0 in the joint advisory. | Malware name | June 2021 | Date not established | Confirmed | CISA, FBI, MS-ISAC, and international partners |
| LockBit 3.0Third major LockBit variant; the leaked builder later enabled non-LockBit affiliates to deploy it. | Malware name | March 2022 | Date not established | Confirmed | CISA, FBI, MS-ISAC, and international partners |
| LockBit BlackAlternate name for LockBit 3.0 in the joint advisory. | Malware name | March 2022 | Date not established | Confirmed | CISA, FBI, MS-ISAC, and international partners |
Historical timeline
-
LockBit operation launched
LockBit name appears
LockBit-named ransomware appeared on Russian-language cybercrime forums in January 2020.
Evidence status: officially confirmed ConfirmedRelated: ABCD ransomware
-
LockBit alias observed
LockBit 2.0 / LockBit Red appears
The joint advisory records the appearance of LockBit 2.0, also known as LockBit Red.
Evidence status: officially confirmed Confirmed -
LockBit alias observed
LockBit 3.0 / LockBit Black emerges
The joint advisory records the emergence of LockBit 3.0, also known as LockBit Black.
Evidence status: officially confirmed Confirmed -
LockBit alias observed
LockBit Green appears
The joint advisory reports that LockBit Green incorporated Conti ransomware source code; this is code lineage, not proof of shared operators.
Evidence status: officially confirmed High confidenceRelated: Conti
-
LockBit infrastructure disrupted
Operation Cronos disrupts LockBit infrastructure
The NCA announced an international operation that infiltrated LockBit's network and took control of services, including its leak site. The event is a disruption, not a claim that all later activity ceased.
Evidence status: officially confirmed Confirmed
Lineage and relationships
| Related actor or family | Relationship | Period | Confidence | Evidence summary | Sources |
|---|---|---|---|---|---|
| Contioperation | Code overlapsupported · undirected | From January 2023 | High confidence | The joint LockBit advisory reports that LockBit Green incorporated Conti ransomware source code. Code reuse is not evidence that the operations shared leadership.
| CISA, FBI, MS-ISAC, and international partners |
| ABCD ransomwareransomware family | Predecessorconfirmed · directed | From September 2019 | Confirmed | The joint LockBit advisory explicitly calls ABCD ransomware the predecessor to LockBit. This describes ransomware lineage and does not by itself prove uninterrupted operator identity.
| CISA, FBI, MS-ISAC, and international partners |
Predecessors
Successors
None established.
Splits and mergers
None established.
Suspected affiliate relationships
None established.
MITRE ATT&CK integration
No explicit MITRE ATT&CK group mapping is published for this source label. Software entries and fuzzy name matches are not promoted to group mappings.
External intelligence references
- Casualtek/RansomchatsCasualtek · dataset provenance · context only
- Understanding Ransomware Threat Actors: LockBitCISA, FBI, MS-ISAC, and international partners · government advisory · primary authoritative
- The NCA announces the disruption of LockBit with Operation CronosUK National Crime Agency · law enforcement · primary authoritative
- Mikhail Pavlovich MatveevFederal Bureau of Investigation · law enforcement · primary authoritative
- Russian National Charged with Ransomware Attacks Against Critical InfrastructureU.S. Department of Justice · law enforcement · primary authoritative
- Terms and ConditionsUK National Crime Agency · publisher terms · context only
- Privacy PolicyFederal Bureau of Investigation · publisher terms · context only
Confidence and evidence notes
Confidence applies to each individual alias, event, or relationship—not to the actor page as a whole. “Confirmed” requires explicit authoritative attribution or multiple strong independent sources. Moderate, low, disputed, and unknown entries retain the source's uncertainty. A malware-family name is not automatically an actor identity, and shared code or affiliates do not prove shared leadership.
Ransomware notes
Browse Lockbit notesThe explicit archive alias mapping connects this Ransomchats actor label to the ThreatLabz family Lockbit. Its 5 archived notes are counted and searched separately from the negotiation records below.
Search within this collection
Negotiation records
| Participants | Source | Archive status | |||
|---|---|---|---|---|---|
| Not recorded | **************************149576 | 17 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************83E824 | 3 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************E06EBD | 27 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************6B2E47 | 27 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | 0E1263992076698458ABCB025007C6FF | 42 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************E3E6E9 | 25 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************830677 | 37 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************138292 | 106 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************FD63B4 | 8 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************58E425 | 29 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************5571ED | 6 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************3FB886 | 34 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************D530E1 | 52 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************E1F5B5 | 27 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************AF75A0 | 8 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************7E0E3E | 94 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************DD3ED9 | 93 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | 124 | 50 | Lockbit3.0, Victim | JSON | Indexed |
| Not recorded | 154 | 137 | Lockbit3.0, Victim | JSON | Indexed |
| Not recorded | 206 | 4 | Lockbit3.0, Victim | JSON | Indexed |
| Not recorded | 36 | 49 | Lockbit3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************83E679 | 43 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************C28148 | 99 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************FFFFFF | 70 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************EDEF83 | 43 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************48F187 | 56 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************6061AC | 66 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************8FD3F5 | 28 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************A3A3A4 | 8 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************645926 | 17 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************1E97B3 | 25 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************D81BF2 | 20 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************E3E68C | 103 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************21837D | 237 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************C0C807 | 29 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************B8DC6D | 78 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************4E978C | 30 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************888989 | 215 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************DFC2C5 | 73 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************CED340 | 21 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************89AFE8 | 39 | LockBit 3.0, Victim | JSON | Indexed |
| Not recorded | Chat: *************7240FE | 34 | LockBit 3.0, Victim | JSON | Indexed |
No matching records
No records match the current filters. Remove one before blaming the archive.