IPCRIME Underground Atlas — an independent, source-grounded editorial reference. Last reviewed November 20, 2026. This is not a live investigative finding.
LockBit became one of the most prominent ransomware-as-a-service brands, using affiliates to intrude into organizations and public-facing leak pages to pressure victims. Operation Cronos in 2024 disrupted infrastructure and exposed parts of the operation, but a disruption should not be described as the permanent elimination of every affiliate or reused tool.
Known aliases, focus and analytical scope
Aliases: LockBit 2.0; LockBit 3.0; LockBitSupp. Focus: Extortion and affiliate operations. The designation identifies a research cluster or operational brand; it does not by itself establish membership, criminal guilt or one universal operator.
Reported activity and patterns
Investigations describe a commercial division of labor between platform operators and affiliates; observed intrusions have involved compromised access, lateral movement, data theft and encryption. Different affiliates use different entry methods. A leak-site victim label is an extortion claim, not independent confirmation of the actor’s access or data theft.
What defenders and investigators can corroborate
Compare initial access events, privileged logons, external data-transfer records, encrypted file patterns and incident-response evidence. For organizational attribution, seek corroborated forensic indicators rather than matching only a ransom note or brand name.
Attribution and evidence limits
Public attribution to named people and the status of criminal proceedings must be distinguished from proven convictions. Operator control and the activity of individual affiliates can change rapidly.
IPCRIME is an independent publication, not a law-enforcement service. We distinguish allegations, vendor intelligence assessments, and established findings. This profile provides defensive context, not an accusation against any individual.
Source: UK NCA — Operation Cronos. Recorded by IPCRIME on November 20, 2026; verify updates against the original source.