Back to blog
Hacks célèbresfuite donnéesAuthentification

Florida DAVID Database: 200,000 Driver Records Claimed by ShinyHunters via a Police Account

Published on 2026-09-125 min readCleanIssue

> TL;DR: Florida's Department of Highway Safety and Motor Vehicles (FLHSMV) confirmed that an international cybercrime organization accessed the DAVID driver database, with the breach discovered September 4, 2026. The ShinyHunters extortion gang claims more than 200,000 driver records stolen. Per the agency, the attacker used compromised credentials belonging to a Plant City Police Department user, "improperly stored on the employee's personal electronic device." ShinyHunters tells a different story: a password reset flaw, access to multiple accounts (DMV employees, an FBI agent), and enumeration of record IDs starting September 3.

Two diverging versions — and why it matters

The official version (one account, credentials stored on a personal device) and the attackers' version (a reset flaw, multiple accounts, mass enumeration) are not cosmetic differences: they demand different remediations. A stolen credential on a personal phone is fixed with BYOD rules and MFA. A password-reset flaw allowing takeover of arbitrary accounts — including an FBI agent's — is a product defect that potentially affects every user of the system.

ShinyHunters' published evidence leans toward an extensive compromise: the group shared a DAVID record for Jeffrey Epstein (personal and vehicle information) and described systematic harvesting by iterating over record IDs. The agency has confirmed neither volume nor method, deferring to an ongoing criminal investigation — the Florida Attorney General, Florida Digital Service, and Florida Department of Law Enforcement are all involved.

Why this matters to you

DAVID is exactly the kind of system found in every B2B SaaS: a high-privilege back office where institutional accounts (customers, partners, authorities, support) access individual records — in your case, employee files, payslips, health data, or identities. The three failures in this incident are the three back-office classics:

  • credentials living outside the controlled perimeter (personal device, no password manager, no effective MFA);
  • an under-verified password reset flow — the mechanism meant to rescue authentication becomes the primary attack path;
  • enumerable records: iterating over sequential IDs and harvesting complete profiles means no rate limit or anomaly detection triggered across tens of thousands of requests.
  • What to do

  • Ban storage of professional credentials on personal devices — and make it detectable: scanned secrets, unexplained sessions, logins from unmanaged devices.
  • Enforce phishing-resistant MFA on every access to personal data, with no exception for "institutional" or "trusted" accounts — those are precisely the targets.
  • Audit the password reset flow as a standalone attack surface: progressive identity verification, user notifications, enumeration lockouts.
  • Detect harvesting: a legitimate account consulting hundreds of sequential profiles in a short window is a cheap, simple alert signature — it apparently failed here.
  • Prepare for narrative divergence: when a gang claims and the institution minimizes, only independent investigation establishes the real perimeter. Preserve access logs BEFORE you need them.
  • The broader lesson

    The same ShinyHunters gang appears across this season's cases (Brevo/Trezor via ShipMonk, the Odido claim, and now Florida). Extortion groups are industrializing: one access, one database, one ransom demand, one public leak on refusal. The question is no longer "are our passwords strong" but "how many records can one compromised account extract overnight, and what stops it."

    Building HR, payroll, or recruiting software? CleanIssue performs security audits for HR SaaS in real-world conditions, no source code access needed. For a first read of your exposure, start with an external review of your application.

    Sources

    Related services

    If this topic maps to a real risk in your stack, these are the most relevant CleanIssue audits.

    Need an external review of your HR SaaS?

    Share your product, stack, and client context. We will come back with the right review scope.

    Discuss your audit