securityprivacy

Your Driver's License Is Being Sold on the Dark Web

A breach at an identity verification company exposed tens of millions of government IDs. What happened, who was affected, and what to do now.

In late October, security journalist Brian Krebs reported that images of tens of millions of U.S. and Canadian driver’s licenses were being offered for sale on the dark web. The source, Krebs reported, appeared to be an identity verification company — a service that businesses use to verify that the person signing up is who they claim to be, typically by collecting a photo of a government-issued ID during the account creation process.

If you’ve ever had to photograph your driver’s license or passport to open a financial account, sign up for a gig work platform, or verify your age on a regulated service, there’s a reasonable possibility that image is now somewhere you didn’t intend it to be.


Why Identity Verification Companies Have So Much Data

Identity verification (IDV) services occupy a specific position in the digital identity ecosystem. When a fintech app, a cryptocurrency exchange, a rental platform, or an age-restricted service needs to verify the real identity of a user, they typically don’t build their own verification system. Instead, they integrate an IDV provider’s SDK or API.

The user gets redirected to the provider’s interface, photographs their government ID, often photographs their face for a liveness check, and submits. The IDV provider runs checks — validating the document format, checking for signs of tampering, matching the face to the document — and returns a pass or fail to the requesting service.

What happens to the document image after verification varies by provider and is rarely clearly disclosed to the user. Some providers claim to delete images within a defined period. Others retain them indefinitely for fraud prevention, compliance purposes, or model training. Many don’t specify retention periods in their consumer-facing disclosures.

The result is that IDV companies accumulate enormous archives of government ID images — passports, driver’s licenses, national identity cards — along with biometric face captures, all linked to real identities. This makes them exceptionally high-value targets for breaches.


The IDScan.net Case

The breach Krebs investigated involved IDScan.net, a New Orleans-based identity verification company. The company confirmed it was investigating. At the time of reporting, the precise scope of what was exposed — how many individuals, which document types, what time period — had not been fully disclosed.

The nature of the data being sold was clear from the listings: government ID images, not just metadata. This matters because a photograph of a driver’s license contains everything an identity thief needs to open fraudulent accounts: full legal name, date of birth, address, ID number, and a visual reference for synthetic identity creation.

This was not an isolated incident. In the same period, a separate breach at a Texas state agency exposed passport numbers and driver’s license information for approximately 3.09 million people. An earlier 2026 breach at AssuranceAmerica, a U.S. insurance provider, affected 6.9 million people’s driver’s license numbers. A researcher documented a separate breach exposing “tens of millions” of driver’s license numbers via a compromised identity verification pipeline distinct from IDScan.

The pattern across these incidents is consistent: identity documents are increasingly being collected by third-party services — sometimes with explicit user awareness, sometimes as a background step in a process the user barely noticed — and those services are being breached.


What Attackers Do with Government ID Images

A complete government ID image is more useful to a fraudster than a list of Social Security numbers or email addresses, for several reasons.

Identity fabrication: A real person’s ID with a substituted face photo creates a synthetic identity that passes basic document validation checks used by banks, telcos, and other regulated services. The underlying data is real; the person using it isn’t.

Account takeover via social engineering: Customer service agents at financial institutions, telcos, and email providers can often be persuaded to reset credentials if the caller “proves” their identity with a document. A real ID image provides that proof.

Credit fraud: Government ID data is sufficient to open credit card accounts, take out personal loans, or apply for benefits in someone else’s name. The more complete the data (ID number, date of birth, address), the easier the fraud is to execute before the victim notices.

Dark web dossier building: Individual stolen records are often combined with data from other breaches to create comprehensive profiles. A driver’s license image combined with a password from a credential dump and a Social Security number from a healthcare breach creates a package that enables a wider range of fraud.


How to Know If You Were Likely Affected

The specific companies whose data was exposed won’t all send breach notification letters promptly, and in some cases may not be required to under applicable state laws depending on the data types involved.

The practical question is: which services have asked you to photograph a government ID in recent years? The list is longer than most people realize.

Services that commonly require ID verification:

  • Cryptocurrency exchanges (virtually all of them, under KYC requirements)
  • Gig economy platforms (Uber, Lyft, DoorDash, TaskRabbit, etc., for driver/provider verification)
  • Online alcohol and cannabis retailers (age verification)
  • Some fintech banking apps (account opening)
  • Rental car platforms
  • Firearms purchase platforms
  • Some voting or civic platforms
  • Some healthcare or prescription delivery services

Each of these integrates an IDV provider. You’re not necessarily interacting directly with the IDV company — you may have never heard of IDScan.net — but your document image may have been stored there.


Steps to Take

Monitor your credit actively. A government ID breach is a trigger for placing a credit freeze with all three major bureaus — Equifax, Experian, and TransUnion. A freeze prevents new credit accounts from being opened in your name without an explicit unfreeze, which a fraudster using your ID cannot do.

Check for fraudulent accounts. Review your credit reports for accounts you don’t recognize. In the U.S., AnnualCreditReport.com provides free weekly reports from all three bureaus. Any unfamiliar account deserves immediate investigation.

Enable alerts on existing financial accounts. Banks, credit card companies, and investment platforms all offer real-time transaction alerts. Enable them. A fraudster using your ID to log into an existing account generates a transaction trail; catching it quickly limits the damage.

Be skeptical of ID replacement scams. Breach notification letters sometimes trigger secondary scams: emails or calls claiming to be “identity restoration services” that offer to help for a fee, or that ask you to provide additional verification. Legitimate breach remediation from a company you have an account with will not ask you to pay a fee or to provide more identity information through an unsolicited outreach.

Replace compromised credentials if you can. You can’t change your date of birth or legal name, but you can apply for a new driver’s license with a new number in some states. Some states issue a new number on request if you provide documentation of identity theft. Passports can be reissued if you can document that the existing one has been compromised. Contact your state’s DMV and check U.S. State Department guidance for passports.


The Structural Problem

The IDV industry exists because businesses need to verify identity to comply with regulations and reduce fraud. That’s a legitimate function. The problem is that the architecture creates a concentration of identity data — millions of government IDs in one place — that is exactly the kind of high-value target that sophisticated attackers prioritize.

There are no consumer-side controls over how IDV companies retain data. When you photograph your driver’s license for a gig platform’s onboarding flow, you’re not making a choice about IDScan.net — you’re making a choice about the gig platform, and IDScan.net is an invisible sub-processor of that choice.

This is a reasonable place to be uncomfortable. Regulatory frameworks in some jurisdictions are beginning to address data retention requirements for IDV services, but enforcement is inconsistent and notification requirements lag behind breach timelines.


Storing Your Own ID Documents Privately

A parallel issue, separate from IDV breaches, is where you store your own copies of government documents.

Many people photograph their passport or driver’s license and keep the image in an email draft, a cloud photo library, or a note-taking app — for convenience when they need to reference a document number or provide a copy of their ID quickly. Those storage environments are not particularly secure for this category of data.

An encrypted personal file storage environment with explicit security controls is a more appropriate home for government document scans. daftei stores files under AES-256 encryption at rest and TLS 1.3 in transit, with 5 GB free and unlimited storage on Pro. Your documents are accessible to you and not to the advertising or AI training ecosystems that make photo libraries and note apps risky for sensitive content.

The IDV breach is a reminder that government IDs have a long exposure lifecycle once they enter any third-party system. Minimizing the systems that hold copies of them, and choosing those systems carefully when storage is necessary, is part of managing the risk.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts