IDScan.net Data Breach: What Happened and What You Should Do
IDScan.net disclosed a data breach affecting an unconfirmed number of people. Here's what is currently known about the incident, what information may have been exposed, and steps you can consider taking.
- Company
- IDScan.net
- People affected
- Unconfirmed
The 153 million+ driver's license figure comes from the Nexus dark-web service and has not been confirmed by IDScan.net. Use company or regulator figures if they are later published.
- Incident date
- Not yet disclosed
- Discovered
- September 1, 2026
- Disclosed
- September 1, 2026
- Information exposed
- Possibly: Government identification, Name, Physical address, Date of birth, Other personal information
- Status
- Under investigation
Company website notice says the investigation is ongoing, systems were secured, third-party specialists were engaged, and it is cooperating with federal law enforcement. KrebsOnSecurity reported the Nexus marketplace went offline shortly after its story.
What happened in the IDScan.net breach?
How the attacker got in
Under investigation. Dark-web operators claimed continuous exfiltration from a major identity verification company; IDScan.net has not published a confirmed root cause.
Reports conflict
Timeline of what is known
- 01Not yet disclosedUnauthorized access
- 02September 1, 2026Breach discovered
- 03September 1, 2026Breach disclosed publicly
- 04September 4, 2026Affected individuals notified
Dates come from the sources listed at the bottom of this page. Separate events are kept separate; where a date has not been disclosed, it says so.
What information was exposed?
The categories below come from IDScan.net's disclosure and the sources listed on this page. Each is labeled by what the evidence supports. Categories not mentioned in any source are not listed, even if they are common in similar breaches.
Government identification
Company notice: driver's license or other government-issued identification numbers may be in affected cloud-account data. Dark-web sellers also advertised full license image scans (including infrared/UV variants in some samples); image inventory is not company-confirmed.
Name
Company notice: full names may be in affected data.
Physical address
Typically present on scanned driver's licenses; not listed in the company's September 4 notice fields.
Date of birth
Typically present on scanned driver's licenses; not listed in the company's September 4 notice fields.
Other personal information
Nexus also claimed identification cards, travel/international IDs, and medical cards (including some dispensary cards); not listed in the company notice.
Why this information matters
The risks below are the ones associated with the categories of information involved in this breach. This describes how exposed information can be used in general. It does not state that any of this has happened with data from this incident.
Information from one breach can sometimes be combined with information from other breaches or public sources. A name and email address on their own are limited. Paired with a date of birth from one leak and an address from a people-search site, they become enough to answer a security question or make a scam call sound informed.
Whether the data from this breach has been sold, shared, or used is not known unless a source on this page says so. Where that is documented, it appears in the "What happened" section above.
If you were affected, consider doing these things now
Practical steps for this breach, in rough order of priority. None of these require buying anything. Monitoring services, including ours, are one option among several.
- 01Follow the instructions in any notice you receive from IDScan.net, including enrollment in the complimentary monitoring if you are eligible.
- 02If you have questions about the notice or enrollment, call 1-833-516-2980 (Monday–Friday 8:00 a.m.–8:00 p.m. ET, excluding holidays) or write to the Metairie address on the company notice.
- 03Treat any unsolicited message about driver's licenses, ID verification, Hertz, dispensaries, or this incident as potential phishing until you verify it independently.
- 04If your driver's license was scanned at a business that uses third-party ID verification, watch for identity theft and new-account fraud.
- 05Consider a credit freeze with Equifax, Experian, and TransUnion, especially if government ID numbers or images may be circulating.
- 06Monitor credit reports and financial accounts for accounts you did not open.
- 07Be cautious of deepfake or cloned-ID scams that use stolen license images.
- 08Consider a personal information monitoring service.
AI Protection
Monitoring, alerts, and recovery help for what comes after a breach.
A breach puts information you can't take back into circulation. AI Protection watches for it being misused, alerts you when something changes, and helps you recover if something goes wrong. It cannot undo the breach or retrieve data an attacker already holds.
How one breach can contribute to a larger exposure footprint
A possible risk pattern, not a description of this incident. Each step is something that can happen after a breach. Nothing here states that it has happened with data from this incident.
Illustrative pattern- Step 1
One breach
A single company's records are accessed without authorization.
- Step 2
Personal information is exposed
Some categories can be changed afterward. Others, like a name or date of birth, can't.
- Step 3
It may remain accessible
Copies of breached data can persist well beyond the original incident.
- Step 4
Sources can be combined
Fragments from different breaches and public sources may be assembled into a fuller profile.
- Step 5
More targeted attempts
A fuller profile can make fraud, impersonation, phishing, or social engineering attempts more convincing.
A breach is an event. Exposure can last longer.
A password can be reset and a card reissued. Some information can't be replaced, and that is the part that stays useful to someone attempting fraud later. This does not mean fraud will occur. It means the risk does not close when the news cycle does.
Involved in this breach and hard to change
None of the categories reported in this breach are in the hard-to-change group. Changeable items like passwords and account numbers should still be addressed.
What IDScan.net has done so far
Only actions the company has announced or that are documented in the sources below. If something you'd expect to see isn't here, it hasn't been announced as of the last update.
Sources
Primary sources first: company disclosures, regulator and attorney general filings, SEC filings, court documents. News reporting is listed as secondary. Where reports conflict, the conflict is noted in the "What happened" section rather than resolved silently.
Last updated September 9, 2026 · First published September 4, 2026
Questions about the IDScan.net breach
Take control of what happens next.
Monitoring for misuse of your information, alerts when something changes, and a real person to call if something goes wrong. Plans from $7 per month. Cancel anytime.