Ransomware gang
LockBit 3.0
Claims on its leak site since 29 June 2022, number 152 of all gangs in the last 12 months
- Claims, 12 months
- 1
- Last 30 days
- 0
- All claims
- 2,016
- Last claim
- 5 December 2025
ransomware.live lists it as descended from LockBit 2.0. It lists LockBit 5.0 as its successors.
Where its claimed victims are
Sectors
Claims matched to an official notice
12 organisations LockBit 3.0 claimed also filed a breach notice with a regulator, all of them after the claim (a median of 108 days later). Matched by name: the notice does not say who the attacker was.
- Intelliloan, Inc.
Claimed 13 April 2025 · notice filed with the California Attorney General 25 September 2025 - Allied Telesis, Inc.
Claimed 27 May 2024 · notice filed with the California Attorney General 21 April 2025 - Sierra Construction Company, Inc.
Claimed 19 April 2024 · notice filed with the Washington Attorney General 30 October 2024 - David’s Bridal
Claimed 22 January 2024 · notice filed with the Washington Attorney General 13 September 2024 - Consulting Radiologists LTD. (“CRL”)
Claimed 8 May 2024 · notice filed with the California Attorney General 14 June 2024 - Planet Home Lending, LLC
Claimed 17 November 2023 · notice filed with the Washington Attorney General 23 January 2024 - Hi-School Pharmacy
Claimed 28 November 2023 · notice filed with the Washington Attorney General 6 December 2023 - World Learning, Inc.
Claimed 7 June 2023 · notice filed with the Washington Attorney General 27 November 2023 - Bayside Interiors, Inc.
Claimed 9 April 2023 · notice filed with the California Attorney General 26 July 2023 - iSpace, Inc.
Claimed 24 February 2023 · notice filed with the California Attorney General 31 May 2023 - Crystal Creamery, Inc.
Claimed 3 February 2023 · notice filed with the California Attorney General 3 March 2023 - Lincare Holdings Inc.
Claimed 30 October 2022 · notice filed with the California Attorney General 3 January 2023
Government advisories
What a claim is, and is not
A claim is a ransomware gang naming an organisation on its leak site, usually to pressure it into paying. It is the gang’s word: some claims are false, recycled from older breaches or exaggerated, and a claim says nothing about whose personal data, if any, was taken. That is why we count claims but do not list the organisations, and why a breach goes on the tracker as confirmed only when the organisation or a regulator says so.
How this is counted
Claims as collected from the gangs’ leak sites by ransomware.live, which says itself that they are unverified. We read its list every day and keep only counts: by month, by the victim’s country and by sector (as ransomware.live classifies them). Matches with official notices are by the organisation’s name, from 30 days before the claim to a year after it, against California’s and Washington’s full breach registers and every official notice on the tracker. A match is not a confirmation rate: those registers only see breaches of their own residents, and names are written differently. We never link to or visit leak sites.
From the data breach tracker: official notices, breach databases and the news, every fact with its source. Open data (CC BY 4.0) · How the tracker works · Found a mistake? Tell us and we correct it.