IDScan.net Breach: 153M Claimed, 13M Filed


 (The image is AI-generated) 

 

 

Last updated: November 15, 2026

Two breaches disclosed in September 2026 show how identity and health data can be exposed in very different ways. IDScan.net, a Louisiana identity-verification vendor, confirmed that an intruder had access to its VeriScan cloud platform after a criminal service called Nexus advertised scans of more than 153 million driver’s licenses. Astrana Health, a California healthcare management company, told the SEC that phone-based social engineering gave attackers access to its systems.

The scale of the IDScan incident is still disputed, and neither company has published a full list of what was taken. This article separates what is confirmed from what attackers or the companies claim, and it corrects several details in the earlier draft.

Key takeaways
  • IDScan.net says an unauthorized party was in its VeriScan cloud from April 4 to September 2, 2026. The 153 million figure is the seller's claim. State filings list about 13 million people.
  • Journalist Brian Krebs traced sample records to IDScan.net, and the FBI is looking into the incident. Canada’s privacy commissioner opened an investigation on September 21.
  • Astrana’s SEC filing describes callers who impersonated staff and spoofed the company’s main phone number. By its November 10-Q, Astrana said private information was accessed and acquired.
  • Neither company has named a threat actor, and affected-person counts remain unclear for Astrana.
  • For companies, the practical lessons are data minimization, vendor oversight and call-back verification.

IDScan.net: what happened

IDScan.net is based in the New Orleans area and sells ID-scanning and verification tools to businesses that check customers’ identity or age. Krebs reported that its clients include Hertz, Target, FedEx and Planet 13 dispensaries. The company’s own materials say it performs more than 21 million verifications a month. That is a marketing claim, and I could not verify it independently.

The breach became public through Krebs. On September 1, he reported that a new service called Nexus, advertised on the Russian-language Exploit forum, was selling searchable scans of identity documents. Nexus claimed more than 153 million driver’s licenses from the United States and Canada, over 10 million ID cards, more than 3 million travel documents and at least 579,000 medical cards. Krebs asked people for permission to search for their licenses, and compared timestamps on stolen images with when owners had their IDs scanned, including at Hertz and Planet 13. He reported that the trail pointed to IDScan.net.

Krebs also reported that Nexus listed a license for Defense Secretary Pete Hegseth and one for an FBI assistant director. Other outlets describe the Hegseth listing as reported, not independently verified. The FBI said it was looking into the incident, and Krebs reported that the New Orleans field office opened an official inquiry. Nexus went offline soon after publication, but copies of the data could still circulate.

IDScan.net: 153 million claimed, 13 million filed

IDScan.net’s notice, posted on September 4 and updated September 29, says it learned on or around September 1 that data may have been accessed without authorization. It later said an unauthorized third party accessed part of its cloud environment between April 4 and September 2, 2026, and that the event was limited to its VeriScan platform. The categories of data depend on what each customer collected, and can include names, contact details, dates of birth, and license, passport or other government ID numbers. That is the company’s own account of the intrusion. One security outlet also reported that the first notice carried a noindex tag that kept it out of search results. I could not confirm that detail from a primary source.

The numbers do not match. The 153 million figure comes from Nexus’s sales listing. State filings, including an Oregon attorney general listing reported on September 18, put the total at 13,000,000 individuals, and the Texas listing also shows 13 million in total. IDScan has not publicly confirmed either number in its notice. A tracker covering the filings notes the company’s public notice still gives no count.

The date range also matters. The April 4 to September 2 window describes when the intruder had access, according to IDScan. It does not say when each person’s ID was scanned. The earlier draft repeated a claim that the operators had been extracting data for more than a year, and I found no source for it, so I removed it.

Krebs said a Nexus search returned an estimated 11.5 million pages of results, and a security outlet quoted him as saying the seller was likely not exaggerating the 153 million figure. That is an informed judgment, not a measurement. The gap between 13 million people and 153 million scans could reflect multiple scans per person, different counting methods, or inflated claims.

IDScan.net: the response

IDScan says it secured its systems, hired outside specialists and is cooperating with law enforcement. It offers free credit monitoring, and its October 16 notice for individuals in Canada says it is not aware of any misuse of personal information. Canada’s Office of the Privacy Commissioner opened an investigation on September 21 into the company’s safeguards and the adequacy of its notifications under PIPEDA.

Litigation followed within days. Court-docket trackers count at least 18 class actions in the Eastern District of Louisiana by October 8, with the first filed on September 2 and several cases showing stays. Counts differ between trackers, so treat the figure as approximate.

Astrana Health: a phone-based social engineering attack

Astrana Health (Nasdaq: ASTH) is a California-based healthcare company whose subsidiary, Astrana Health Management, handles administrative work for physician groups. In an SEC Form 8-K filed on September 23, it reported a material cybersecurity incident. According to the filing, attackers impersonated company personnel, spoofed the company’s main corporate telephone number and called employees to obtain access to systems.

Astrana said it detected the activity, engaged a third-party forensics firm and notified law enforcement and regulators. It said it reset affected credentials, restricted remote access tools, restored some systems from clean backups and improved monitoring. The company determined the incident was material as of September 22, citing the potentially sensitive nature of the data. All of this is Astrana’s own account.

The filing said Astrana believed certain private information on its servers had been accessed or acquired, and that it was still assessing whether patient, employee, provider, business or financial data was involved. It also said it did not expect a material effect on its finances at that time. No threat actor group had publicly claimed the attack when I looked, and the company has not confirmed ransomware.

The attack worked on trust in a number that looks internal. A spoofed number costs an attacker little, and the person who answers sees the company’s own caller ID. For a roundup of other incidents from the same month, including healthcare cases, see our September 2026 breaches summary.

Two breaches, two lessons

The vectors differ. IDScan’s intrusion involved a cloud platform that stored customer scans, while Astrana’s began with a telephone call to employees. The data also differs: ID numbers and document images are hard to replace, and health information carries its own harms and regulation, including HIPAA.

Both cases show third-party concentration. IDScan sits between many businesses and their customers’ identity documents, so one intrusion can reach people who never dealt with it directly. Astrana is a management services organization serving provider groups, so a breach affects people who never used the company’s name. Both also show how slowly facts emerge. IDScan’s notice left out a count and an entry method, and Astrana’s affected-person count remained undisclosed. For a different kind of 2026 incident, see our write-up of the Binance hack.

Claim check

This table covers claims in the earlier draft and early coverage. Confirmed means official records or reliable reporting support it. Company claim means a company asserts it about itself. Unverified means I found no solid source, or it is a criminal claim. Wrong means current sources contradict it as written.

 

Claim Status Note
Nexus advertised 153M+ licenses, 10M+ ID cards, 3M+ travel documents and 579,000 medical cards. Unverified The seller's claimed totals. Krebs verified sample records.
Krebs traced sample records to IDScan.net. Confirmed He compared scan timestamps with real visits to Hertz and Planet 13.
The FBI is investigating. Confirmed The FBI said it was looking into the incident. The New Orleans office opened an inquiry, per Krebs.
A license for Defense Secretary Pete Hegseth was listed. Confirmed Reported by Krebs. Other outlets say "reportedly".
Operators had extracted records for more than a year. Unverified No source found. IDScan puts access at April 4 to September 2. Removed.
Access ran April 4 to September 2, 2026 and was limited to VeriScan. Company claim IDScan's own account. Investigation is ongoing.
The first notice carried a noindex tag. Unverified One security outlet reported it. No primary source found.
13 million people were affected. Company claim From IDScan's state filings (Oregon, Texas). Its public notice gives no count.
IDScan confirmed that 153 million licenses were stolen. Wrong IDScan has not confirmed that figure.
Canada's privacy commissioner opened an investigation on September 21. Confirmed Under PIPEDA, covering safeguards and notifications.
"Multiple" class actions followed. Confirmed At least 18 by October 8 per a docket tracker. Counts vary.
21M verifications a month, 20,000 locations, 1,000 dispensaries in 19 states, and named customers such as Motorola Solutions and Caesars. Company claim Marketing figures. Krebs names Hertz, Target, FedEx and Planet 13 only.
Astrana filed an Item 1.05 8-K on September 22-23. Confirmed Report date September 22, signed September 23. Materiality as of September 22.
Attackers impersonated staff and spoofed the main phone number. Company claim From Astrana's SEC filing.
Astrana reset credentials, restricted remote tools and restored systems from clean backups. Company claim Stated in the filing.
Astrana's 2025 revenue was nearly $3.2 billion with more than 600 employee associates. Unverified Not found. Removed.
Astrana does not expect a material financial effect. Company claim September 8-K statement. The November 10-Q says it cannot estimate the full impact.
No threat actor or ransomware confirmed for Astrana. Unverified I found no claim of responsibility. Management called it criminal activity on the earnings call.

Update

Update (November 15, 2026): Astrana’s quarterly report filed on November 6 says certain private or confidential information on its servers was accessed and acquired without authorization. That is firmer than the September wording. It also says the company expects to keep incurring costs, is unable to estimate the full impact, and has been named in several class actions. On its earnings call, management declined to size the impact. For IDScan.net, I found no new official count or named attacker since the October 16 notice.

Change log: November 15, 2026 – rewritten and fact-checked; corrected the access window, scale claims and company details, and added the Astrana 10-Q. November 15, 2026 – first published.

My take

  • These attacks are a serious warning to companies to adopt stronger protection. IDScan.net’s intruder reportedly had access for about five months, and Astrana was reached with a phone call.
  • One reservation: the lesson does not depend on the headline numbers. The 153 million figure is unverified, and 13 million people is still a large exposure. A call for stronger controls is more convincing when it rests on what is confirmed.
  • I have not tested either company’s systems. This view comes from filings, regulator statements and press reports.

What this means for you

If you scanned an ID at a store or rental counter

  1. Watch your credit reports. Consider a fraud alert or a credit freeze with Equifax, Experian and TransUnion, as IDScan advised.
  2. Use the free monitoring if you are notified. IDScan says it offers credit monitoring to potentially affected people.
  3. Be careful with breach-check links. Scammers use these events to send fake notices.

If you run a business

  1. Keep less. Ask vendors how long they retain ID images and whether they can delete them.
  2. Review contracts. Require breach-notification timelines and clear data-retention terms.
  3. Verify callers by calling back. Use a known number, because caller ID can be faked.
  4. Limit remote access. Apply least privilege and require stronger sign-in for remote tools.

FAQ

Were 153 million licenses stolen from IDScan.net?

That is what the Nexus seller claimed. IDScan has not confirmed it, and state filings list about 13 million people.

How did attackers get into IDScan.net?

The company has not said. It reports unauthorized access to part of its VeriScan cloud environment between April 4 and September 2.

Was Astrana hit by ransomware?

Astrana has not said so, and I found no claim of responsibility. Its filings describe social engineering and unauthorized access to data.

Sources

Post a Comment

0Comments

Post a Comment (0)