153 Million Driver's Licences - The Scanner at the Front Desk, and the Shop That Sold What It Saw
23 minAudio
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! A dark web shop, 153 million driver's licence scans, an FBI investigation, and the scanner at your front desk. What was found. On 1 September, KrebsOnSecurity reported a dark web service called "Nexus" advertising more than 153 million US and Canadian driver's licence scans, plus 10 million+ ID cards, 3 million+ travel documents and 579,000+ medical cards. Records contained six images per document - front and back in normal, infrared and ultraviolet light - with date and time stamps. The listing appeared on a Russian-language forum on 31 August. The FBI's New Orleans field office opened an investigation the day Krebs published and confirmed it publicly to Reuters on 2 September. The Nexus site went offline hours after publication. Four class actions were filed on 2 September in the US District Court for the Eastern District of Louisiana. The important qualifier. The lawsuits name identity-verification vendor IDScan.net, but the company has NOT confirmed a breach. It says it is working to validate the information, has not reached conclusions on the nature or scope of any incident, and has secured systems, preserved logs, engaged outside counsel and forensics, and contacted law enforcement. Krebs's evidence is correlative: he found his own licence and nine of a dozen consenting volunteers' licences, and every timestamp matched a moment the person handed a licence to a business - usually a car rental counter. IDScan.net's documentation describes infrared and ultraviolet document scanning, matching the image types in the dump. Compelling, but not proven. A correction worth noting. Early coverage listed brands from IDScan.net's public customer page. Caesars Entertainment stated on 2 September that it has not been a client, stopped using the relevant product in February 2025, had no active accounts at the time, and did not authorise data retention. Also unknown: when collection began (the "over a year" claim comes from the seller's own advertisement), and whether the dataset still circulates. There is no legitimate service where an individual can check exposure. What Australian businesses should do. If you photograph or scan customer ID - real estate, recruitment, RTOs, conveyancing, gyms, venues, car hire, AML checks - this is your risk profile. Four questions: (1) Do you still hold documents you no longer need? Australian Privacy Principle 11.2 requires destruction or de-identification once the permitted purpose has passed. (2) If you use a third-party verification product, where is the image stored, for how long, and what do your contract terms actually say about retention, deletion on termination, sub-processors and breach notification? (3) Could you record a verification event instead of keeping an image? (4) If your ID store were breached tomorrow, could you say how many documents, whose, and how old? Visit www.kinsoft.com.au to talk through your security and IT needs. Sources: KrebsOnSecurity; Reuters; BleepingComputer; SecurityWeek; CSO Online; TIME; OAIC (Australian Privacy Principle 11).
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
Picture the last time you handed your driver's license to a hotel clerk or, you know, maybe a rental car agent. Right. They slid it onto a little plastic scanner. It flashed a bright light and they just handed it right back to you. Exactly. And you don't even think about it. No, you probably didn't think twice. But what if I told you that mundane little flash of light just turned your physical identity into an infinitely replicable digital ghost? Oh, wow. Yeah, and that ghost is currently up for sale on the dark
web. It really is the ultimate invisible transaction. Right. We have this built -in assumption that once the card is back in our wallet, you know, the interaction is totally over. Right. We just assume. whatever data that little machine captured just evaporates into some secure momentary void. Okay, let's untack this because today's deep dive is a forensic look at a massive and quite frankly staggering dark web data discovery that answers exactly what happens after that scanner flashes. Yeah, it's a huge deal. It really is.
We are going to explore the brilliant investigative methodology used to uncover the source of this massive data dump. And more importantly, the urgent wake up call it provides for absolutely any business that scans IDs. And for you, you know, the person actually handing it over. Exactly. And it is so crucial to state right up front that this isn't just another run of the mill story about a computer network getting hacked. Right. It's bigger than that. Much bigger. Yeah. This is a masterclass in understanding the invisible
pipeline of our most sensitive personal data. It exposes the structural mechanics of how identity works and how it spectacularly fails in the modern digital economy. To really understand why handing over an ID at a front desk is suddenly so incredibly risky, we have to look at where those scanned images ultimately surfaced. We are pulling from an independent investigation into a massive data breach that broke on September 1st. And the sheer scale of the numbers here is, well, it's difficult to wrap your head around. It really is. A Russian
language cybercrime forum was hosting this searchable subscription style dark web service. It was called Nexus. The business model there is actually really important to understand. It's a subscription service. Right. So it operates almost like a legitimate data brokerage or like a streaming platform, but entirely for stolen identities. Wow. Yeah. Criminals aren't buying one ID at a time. They're paying a monthly fee to access this fire hose of raw, searchable human identity.
And the inventory of this Nexus service was breathtaking. We are talking about over 153 million U .S. and Canadian driver's licenses. Just staggering. Plus 10 million state ID cards, 3 million travel documents, and over 579 ,000 medical and cannabis dispensary cards. When you hear a number like 153 million, you really have to contextualize the scale. Yeah, it's massive. That is a massive percentage of the entire adult population of North America. We are not talking about a target. Right. This is an industrial scale of data collection.
But the scale isn't even the most terrifying part, honestly. It's the depth of the data. Yes. Nexus wasn't just selling text data. They weren't just giving subscribers spreadsheets with names, birthdates and, you know, address fields. Right. Which would be bad enough. Exactly. But they were selling the actual high resolution images. Right. And it wasn't just one flat picture per person. Every single record contained exactly six image files. Six. Six. They had the front and the back of the document scanned in normal light. Plus the front and back scanned in infrared
light. And the front and back scanned in ultraviolet light. All of this was tied together with a highly specific date and time stamp in the file name. Which is an incredibly specific, very deliberate. Data architecture. And I have to push back on this because it feels like massive overkill. How so? Well, why would a criminal syndicate care about infrared and ultraviolet images? Doesn't storing six high resolution images per person just make the database pointlessly massive and, I mean, expensive to host? It does take a lot
of space. Yeah. Right. If a fraudster just wants to steal my identity to open a fraudulent credit card or a bank account. Don't they just need the text details and maybe a standard picture of the front of the ID? What's fascinating here is the underlying intent behind why those specific light spectrums are captured and how modern fraud actually works today. Okay. It's all about bypassing automated security. Oh, I see. Yeah. So when an automated banking app or a cryptocurrency exchange asks you to verify your identity by
holding your license up to your smartphone camera, the artificial intelligence isn't just looking at your photo. What is it looking for? It is looking for the hidden physical security features embedded in the card itself. You mean things like the holograms or the micro printing? Exactly. The specialized inks and watermarks that only react to certain light frequencies. Those specific light spectrums, the UV and the infrared, are the precise... details required to prove to a computer that a document isn't a digital forgery. Wait, so how does a 2D image of a UV scan trick
a modern 3D facial recognition or like a banking camera? Through synthetic video, often called deepfakes. Oh, of course. Yeah. If a criminal wants to create a digital spoof of your identity, they take those raw UV and infrared files and feed them into software that creates a virtual camera feed. Wow. When the banking app requests camera access, it gets routed to this virtual feed instead of a real webcam. That is wild. The software then perfectly simulates how light would bounce off those hidden holograms as the
quote unquote card is moved around on screen. No way. Yeah, completely tricking the AI into thinking a legitimate, physical, government issued piece of plastic is sitting right there in front of the lens. That's terrifying. By having these six specific images, it elevates the crime from simple credit card fraud to highly sophisticated, undetectable. biometric impersonation. That is deeply unsettling. So that leaves us with over 150 million of these incredibly detailed, highly weaponized files sitting on the dark web. The
immediate question becomes, how do you even begin to prove where they came from? I mean, they're just anonymous files. Which brings us to the methodology of independent security journalist Brian Krebs, who investigated this dump. And the sleuthing here is genuinely brilliant. It really is. Because it is extremely difficult to look at a pile of 150 million driver's licenses and pinpoint the exact source of the leak. By definition, your ID card is used in dozens of different places over its lifespan. So to find
the source, Krebs didn't just guess. He essentially engineered a control group. Right. He actually found his own driver's license in this Nexus dataset first. Then he went out and acquired explicit consent from over a dozen different people he knew, searched the dark web database for their information, and successfully located nine of their licenses in the dump. Which is the crucial first step. Now he has a controlled sample group to analyze rather than 150 million random data points. From there, he looked at the file names. Remember those exact timestamps
appended to the six images? Yeah, the date and time. He took those timestamps and correlated them with his sample group. He asked those people to check their emails and receipts and matched the exact date and time in the file to the exact moments those specific people had physically handed their IDs to a business. And what did he find? Overwhelmingly, these timestamps matched the exact moments they were standing at car rental counters. That behavioral correlation is just, it's the key to unlocking the whole mystery.
And the detail here is stunning. Two federal employees in his sample data set had been traveling for work. They used their passports to get through airport security. But when they finally got to their destination, they handed their driver's licenses to a higher car company at the desk. Right. Only their driver's licenses were in the Nexus dump. Their passports were completely safe. Wow. And the timestamp on the dark web files perfectly matched the minute they were at the rental car counter, not the airport. That's amazing. Furthermore, Krebs and his own mother handed
their separate licenses to the exact same rental agent at the exact same time, and their file timestamps in the dark web dump were mere seconds apart. The precision there is remarkable. It completely isolates the physical point of compromise down to a single interaction. Here's where it gets really interesting. It's basically... Digital carbon dating. Oh, I like that. You are taking this anonymous artifact, the image file, and using the timestamp to pinpoint the exact moment of exposure. It's like finding a fossil and tracking
it back to the exact second it was frozen in stone, you know, in the hands of a specific vendor. Digital carbon dating is a great way to conceptualize the mechanism. You are tracing the artifact back to its exact origin point in time and space. Yeah. But while that behavioral timestamp correlation is incredibly powerful on its own, it is the technical smoking gun. that really narrows the focus of the investigation. Because Krebs looked at the specific, highly unusual capability of capturing those six images, normal, infrared, and ultraviolet light, he traced that hardware
capability to a company called IDscan .net. They are an identity verification company headquartered in New Orleans, and they are massive. Very massive. They process a staggering 21 million verifications a month across more than 20 ,000 locations. In their own technical documentation, they specifically boast about scanning documents using infrared and ultraviolet light. Which is a highly uncommon capability for standard commercial scanners. Yeah, I'd imagine. Your average $50 flatbed scanner
at a small business does not have infrared and ultraviolet bulbs in it. Right, of course not. It requires specialized hardware integrated with specialized software. And that capability perfectly matches the unique six image architecture of the records found in the dark web dump. It's quite a coincidence. The combination of the digital carbon dating and this rare technical capability is incredibly compelling investigative work. However. We have to put our analytical hats on here. Right. We have to be clear. Yes. And state clearly that in a legal sense is technically still circumstantial evidence. Because the evidence
is compelling but circumstantial, we have to look closely at how the accused company, the authorities and the broader corporate world reacted in the crucial 48 hours following this discovery. Because once this was published. Things moved unbelievably fast. Faster than almost any standard cybersecurity incident timeline I've seen. Yeah. Following the publication of the investigation on September 1st, the FBI's New Orleans field office immediately opened an active probe. Wow, that fast. Within hours of the story dropping,
the Nexus dark website completely vanished. Just gone. It was replaced with a generic message saying the service was no longer available. So they knew they were caught. Exactly. And the very next day, four separate class action lawsuits were instantly filed in federal court against IDscan .net. So you have the federal government and massive civil litigation moving in a matter of hours. The speed of that legal and federal response is a direct reflection of the severity and the sheer volume of the data involved. But this is where we must insert professional qualifiers.
IDscan .net has not confirmed a breach of their systems. They have publicly stated they are urgently investigating to validate the information. They have confirmed they've secured their systems, preserved their logs, engaged outside digital forensics and legal counsel, and are working directly with law enforcement. So they're taking it seriously. Yes, but they have not reached a conclusion about the scope, the nature, or the validity of the incident. In the eyes of the law and professional analysis, this remains an allegation. It is not a proven fact. A court
of law or a final forensic report will ultimately decide what happened. And neither of those things has happened yet. Correct. But the fallout in the meantime has been absolute chaos, which leads us to a fascinating lesson in corporate reaction. Oh, the logo trap. Yes. Early news coverage of this story wrongly implicated several massive global brands, suggesting they were direct victims of the breach simply because their corporate logos were featured on IDscan .net uses customer page. Yeah, that was a mess. Caesars Entertainment, for instance, had to aggressively and publicly
push back. They stated they stopped using the relevant product entirely 18 months prior. in February 2025 that they had no active accounts and they emphatically stated they never authorized data retention in the first place. Right. But I have to ask, how does that even happen? If a massive company like Caesars cut ties 18 months ago, how did they get dragged into a PR nightmare like this overnight? This raises an important question about third party risk and what we might call the logo trap in technology marketing. The
logo trap. Yeah, if a business has ever put a client's logo on their website, or if a company has allowed their logo to be put on a vendor's website, they know exactly how this works. It's just for show. Exactly. Marketing departments love to showcase recognizable brands to build trust. Yeah. But those static web pages are rarely audited or updated when contracts expire. Oh, I see. So in the first 24 hours of a cyber incident, journalists and automated web scrapers are frantically looking for angles. And they find the logo page. They pull that logo page. Suddenly, a brand is
splashed across the headlines as part of a 150 million record data breach, completely inaccurately. Misinformation spreads like wildfire in that initial vacuum of hard facts. The Caesars correction is actually the perfect pivot for us because it proves that this deep dive isn't just about one specific vendor's alleged security failure. It exposes a massive structural flaw in how every single business handles the IDs that you, the listener, hand over to them. Precisely. This
is a story about the real estate agent taking a photocopy of your license for a tenancy application, the corporate recruiter doing a background check, the local gym, the accountant. Anyone. If a business verifies identity in any capacity. This is their risk profile. Which means we need to shift the conversation to the four hard, critical questions of data reality that businesses and the customers who use them must start asking immediately. Let's break them down. Sounds good. Question number one, do you still have them? Meaning, do you still have the data you collected? And this is
often the most quietly devastating question a business can ask itself. Why is that? Because the biggest risk isn't necessarily a sophisticated Russian dark web syndicate hacking into a highly secure server. It's the mundane reality of a business keeping a digital copy of a driver's license from 2019 sitting in a random 2026 email inbox. Or a neglected shared cloud drive. Yeah. Simply because no one ever wrote a policy to hit the delete button. So what does this all
mean? It reminds me of handing over a house key to a plumber. OK, I'm listening. Keeping a 2019 ID in a 2026 inbox is like making a copy of your front door key for a plumber to fix a leak. And then the plumber just leaves that key sitting on the public sidewalk for seven years. That's horrifying. Right. Your locks haven't changed, but your exposure is now infinite. Someone is eventually going to step on it. It's like leaving a rusty bear trap in your hallway. That is a perfect analogy for the mechanism of data liability. If we connect this to the bigger picture, holding
on to data you no longer need. isn't just bad practice in many global jurisdictions. It is a direct violation of the law. Really? Yes. For example, if you look at frameworks like the GDPR in Europe or specific rules like Australian Privacy Principle 11 .2, you are legally mandated to destroy or completely de -identify personal information the second you no longer need it for the purpose you collected it. It's not just a suggestion. No, it's not a gentle suggestion from a regulator. It's a legal requirement. Deleting unneeded data
is unquestionably the single most effective cybersecurity control any business can implement. Because you can't steal what isn't there. Exactly. You physically cannot leak what you do not possess. Which brings us to question two. Where does the scanner actually send the image? This is a fundamental misunderstanding many business owners have. They assume that data routing is a technology question. Right. It is not. It is entirely a contract question. What do you mean by that? How is a data transfer a contract issue? Because the technology just does what the contract allows. When you plug in a
third -party scanner at your front desk, are those images being kept on your company's terms or on the vendor's terms? Oh, I see. Do you actually know where the image is stored, for exactly how long, and who the subprocessors are? Wait, what is a subprocessor in this context? A subprocessor is the vendor's vendor. So you hire a verification company, but they rent server space from Amazon Web Services, and they use a different company for their data backups. The web just expands. The chain of custody gets incredibly complex.
If your direct contract with the vendor doesn't explicitly dictate the retention period and mandate total deletion upon termination of the contract, then the answer to where your data lives is simply whatever the vendor decides. That's terrifying. You've outsourced your compliance, but you have kept 100 % of the liability. Which leads into question three, and this one seems so glaringly obvious in hindsight. Could you just collect less data in the first place? Why are we saving high -resolution images to begin with? It is the question that saves a company the most money
and reduces the most risk, yet it gets asked the least. Why? Because saving everything is usually the default setting on these software platforms. For a vast majority of identity checks, a business only needs to verify a document in that specific fleeting moment. Like at a hotel. Exactly. A hotel just needs to know you are who the reservation says you are. They do not need to keep a high -resolution, six -spectrum, infrared image of your license on file for a decade. That makes sense. Simply recording a text log that
a check was successfully performed on this date by this specific employee against this document number is often completely legally sufficient. Substituting a simple text verification record for an actual replicable image fundamentally changes your entire liability profile. And finally, question four, the hardest question of all. What would you actually do in a breach? If your system was compromised tomorrow, could you tell the authorities exactly how many documents were in it, whose they were, and exactly how old they were? That is the very first question any privacy
regulator is going to ask. And answering, we're not entirely sure, is an incredibly expensive response. I bet. The legal landscape is shifting rapidly here. There are new privacy regulations being proposed globally, including exposure drafts discussed in our sources, that would put in a hard 72 -hour clock on notifying the relevant privacy commissioners of a breach. 72 hours is nothing. It's incredibly fast. You physically cannot meet a 72 -hour legal deadline to report a breach if you don't even know where your scanned
IDs are stored or how many you have. Right. And because identity document images are the literal raw material for identity theft, establishing that the breach caused serious harm. in a legal sense, is almost guaranteed. It's a ticking time bomb for literally anyone with a scanner sitting at the front desk. It truly is. And zooming out from the corporate responsibility, there is a massive looming macro trend here. There is a major policy conflict buried underneath this entire story that we really need to acknowledge. Right now, governments all over the world are
aggressively pushing for mandatory identity verification for a much wider range of everyday online activities. Oh, like age verification. Yes. We are seeing major legislative proposals for mandatory age verification to access certain websites, mandatory ID checks to open social media accounts, and tighter financial KYC, you know, know your customer regulations. And just to be clear, we aren't taking a side on whether those... specific government policies are good or bad, but the sheer mechanics of implementing them are obvious. If you have
more gates, you need more keys. Exactly. Regardless of the political intent, the mechanical consequence of those policies is inevitable. Vastly more of your personal, highly sensitive identity documents are going to flow into third -party vendors. Yeah. They're going to sit in front desk scanners and remote cloud servers operated by thousands of different businesses, many of which have absolutely zero data retention policies in place. It's just a recipe for disaster. Every single new verification requirement is an exponential expansion of the attack surface for criminals. Before we wrap
up, I need to issue a very quick, very important warning for you listening to this deep dive. With a breach this massive, over 150 million records, you might be tempted to go looking for a website to check if your specific ID was caught up in it. Don't do it. Do not do that. Our sources are explicitly clear. The Nexus dark web shop went offline, but the underlying database didn't just evaporate. No, it's still out there somewhere. There is currently no legitimate, secure public lookup service where an individual can check
their status for this specific dump. Exactly. If you see a random website offering to check if your ID is in the Nexus breach, do not type your information into it. Those are very often secondary phishing scams designed to harvest the exact sensitive data you are trying to protect. It is a secondary trap that preys on anxiety, and it leaves us all in a deeply precarious position. It really does. I want to leave you with a final thought to mull over, something that really builds on everything we've unpacked today about the intersection of physical plastic and digital data. Okay, let's hear it. We started by talking
about the physical nature of handing over a card. Yeah. need to be completely reinvented wow has the technology of digital forgery officially
outpaced the technology of plastic cards that is a heavy structural question and it completely reframes how we have to think about who we are on paper or on plastic thank you so much for joining us on this deep dive into the hidden life of your personal data i can guarantee this the next time you're standing at that Higher car counter or checking into that hotel and that little plastic scanner flashes its light You are gonna think twice about exactly where that digital ghost is going. We'll see you next time
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Japanese home goods company Iris Ohyama (online store operator Iris Plaza) found a suspicious file in an external...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Australian online retailer Who Gives A Crap told customers on 7 November 2026 that their information was accessed...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Last week in tech, 7 to 14 November 2026. Microsoft's November Patch Tuesday (10 November) fixes well over a...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Chainalysis disclosed on 30 October 2026 that an external actor using "offensive agentic techniques" accessed...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! NSW Health reported unauthorised access to its Oral Health Fee For Service Scheme website on 29 October 2026;...