iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
In June 2021, Tulsa said attackers had shared more than 18,000 City files online. A June 23 update put the total at 18,938. Most were police records or citations and internal department files, but that file count is not a count of affected people. A July update later reported 27 instances in which Social Security numbers were shared.
What happened in the Tulsa ransomware incident?
The City of Tulsa described the ransomware attack as taking place in May 2021; contemporaneous reporting said the City detected it in early May. On June 22, the City disclosed that attackers had shared more than 18,000 City files on the dark web. Its June 23 update specified 18,938 files. The City’s June 22 notice and June 23 update described the material as mostly police citations and internal department files.
Contemporaneous reporting identified the attackers as the Conti ransomware gang. The City’s public notices cited here referred to the attackers without naming Conti. CyberScoop’s report named the group.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What personal information was included?
The June 23 City update listed names, dates of birth, addresses, and driver’s-license numbers among the information in the files. The material included police records and citations as well as internal department files, so the exposed fields could differ from one record to another.
#1 Best Overall
On June 22, the City said police citations did not include Social Security numbers. In a July 13 update, however, it reported 27 instances in which Social Security numbers had been shared and said it was working to contact those individuals. The later notice is a separate, more specific update: the earlier statement about citations should not be read as proof that no Social Security numbers appeared anywhere in the incident. The July 13 City update provides the later figure.
Were my Tulsa police report details leaked?
The City announced an online lookup for people who filed online Tulsa Police reports from January 1, 2015 through May 6, 2021. The announcement does not establish whether that historical lookup is still operating today. Check the City’s July 13 announcement for the original eligibility details and any information it provides about the tool.
Rank #2
Public Radio Tulsa reported that Chief Information Officer Michael Dellinger recommended making multiple searches because different reports could contain different identifying fields. Public Radio Tulsa’s June 24 report quoted him saying: “While we’re still investigating, some of the files contained personally identifiable information, such as name, date of birth, address and driver’s license (numbers).”
What should people do if they may be affected?
The City’s June 22 notice advised people who had filed a police report, received a citation, made a City payment, or otherwise shared personal information with the City before May 2021 to take precautions. It recommended:
Rank #3
- Made in USA - Proudly produced in Ohio by a Veteran-owned business
- Comprehensive Coverage: This BookFactory log book includes essential fields such as post/shift, time of change, date, weather conditions, and a designated space for detailed notes. This ensures that all relevant information is captured and easily accessible.
- Sturdy Cover: The trans-lux cover protects the log book from wear and tear, ensuring its longevity and maintaining the integrity of your recorded data.
- Essential Security Tool: This log book is an indispensable tool for any organization that values security and accountability. It helps to prevent misunderstandings, improve communication, and ensure a smooth transition between shifts.
- Wire-O with Trans-lux cover, 100 Pages, Dimensions 8.5" x 11" - (Security-Pass-Down) Reorder SKU: LOG-100-7CW-PP(Security-Pass-Down)
- Monitor financial accounts and credit reports for unfamiliar activity.
- Ask card issuers about placing fraud alerts on accounts.
- Change passwords for personal accounts, particularly if a password was reused elsewhere.
- Add authentication measures to personal accounts where available.
The City’s disclosures give file totals and examples of exposed data, not a total number of unique people affected. The 18,938 figure counts files, and the 27 figure counts instances of shared Social Security numbers; neither establishes how many individual residents were affected.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
