Category: Security News

  • 153M Driver’s Licenses Exposed: Where the KYC Industry Broke Down

    153M Driver’s Licenses Exposed: Where the KYC Industry Broke Down

    Key Takeaways

    • Nexus, a new identity theft service that surfaced on the Russian cybercrime forum Exploit, is selling more than 153 million scans of U.S. and Canadian driver’s licenses, along with 10 million national ID cards, 3 million travel/international IDs, and 579,000 medical cards. The data is believed to have originated from images leaked by a KYC (identity verification) vendor based in Louisiana. The FBI’s New Orleans field office launched a formal investigation into the data source on August 31. The sold data also includes driver’s licenses of high-ranking officials such as U.S. Defense Secretary Pete Hegseth. The Nexus seller attached a KrebsOnSecurity reporter’s Virginia driver’s license as a free sample in the initial sales post. The service returns approximately 11.5 million pages of empty search results, with 15 records per page, making the 153 million figure difficult to dismiss as fabrication. A search limited to Canadian driver’s licenses alone extracts about 1.1 million records. The inclusion of high-profile licenses raises the possibility that the breach extends beyond personal data exposure into a national security risk.

    Going beyond a simple incident summary, this analysis examines how the 153 million-record driver’s license breach exposes structural vulnerabilities in the digital identity verification (KYC) industry. It traces how images held by identity verification vendors are converted into dark web merchandise through a single hack or insider leak, and the security and policy implications when high-ranking officials’ identity information is exposed through the same channel. A fact-based, analytical piece that calls for improved data retention practices across the industry.

    Table of Contents

    A breach of 153 million driver’s licenses appears to have originated from a single identity verification (KYC) vendor. The FBI’s New Orleans field office has launched a formal investigation into the source of the breach as of August 31.

    Nexus, a new identity theft service that surfaced on the Russian cybercrime forum Exploit, is selling more than 153 million digital scans of U.S. and Canadian driver’s licenses. This driver’s license breach represents an unprecedented scale for a single data leak incident.

    The seller attached the Virginia driver’s license of a reporter at KrebsOnSecurity as a free sample in the initial sales post—exposing the reporter’s full identity. The data is believed to have come from images leaked by a KYC vendor based in Louisiana. The KYC process typically involves storing the ID images submitted by users on a server and then disposing of the copies. But in this case, it appears that the disposal either never took place or the data resurfaced somewhere along the way.

    The Actual Scale of the Driver’s License Breach

    The index published by Nexus includes 10 million U.S. and Canadian national ID cards, 3 million travel/international IDs, and 579,000 medical cards in addition to driver’s licenses. A search limited to Canadian driver’s licenses alone yields about 1.1 million records.

    Running an empty search within the service returns 11.5 million pages, with 15 records per page. If that math holds, the total comes out to roughly 172.5 million records—more than the 153 million figure the seller is advertising.

    National Security Implications of Senior Officials’ License Exposure

    What sets this incident apart from a routine personal data breach is the fact that U.S. Defense Secretary Pete Hegseth’s license was included in the same dataset. The very fact that high-ranking officials’ identities pass through the same KYC pipeline as ordinary citizens is a national security issue.

    This is where I see the most significance. Identity verification is ultimately a process of confirming “who is who”—but if the system entrusted with that confirmation shares the same vulnerability, the verification itself becomes meaningless. From a practitioner’s perspective, the more often driver’s license breaches of this kind repeat, the more the credibility of the policies that mandated KYC in the first place erodes.

    Dark Web Distribution Structure

    Nexus operates on the Exploit forum and built trust by offering free samples. What distinguishes it from other dark web brokers is the scale of the data. Rather than being sold as “resellable assets,” the data is offered as a “self-service search platform”—so buyers can extract what they need through searches rather than purchasing records one by one.

    The FBI has begun investigating the source, but there is still no official statement on whether the KYC vendor was breached externally or through an insider leak. The fact that it is based in Louisiana is not enough to narrow the scope, given how fragmented the KYC outsourcing market is.

    Structural Vulnerabilities of the KYC Industry

    KYC is mandated across the financial, telecommunications, and cryptocurrency industries. The problem is that there is effectively no industry standard for how long ID images are stored or in what form. Some vendors keep originals for a few months; others keep them for years.

    Minimizing data retention, encrypting uploads immediately, and strictly controlling access permissions are basic practices. Yet only a handful of vendors actually follow them. This driver’s license breach starkly illustrates how those gaps end up turning into dark web merchandise.

    Leaked Data Summary

    Data Type Record Count Risk Level
    Driver’s Licenses 153 million Very High
    National ID Cards 10 million High
    Travel/International IDs 3 million High
    Medical Cards 579,000 Medium

    What You Can Do Right Now

    • Sign up for an identity theft monitoring service (e.g., the U.S. Identity Theft Resource Center, or the Financial Consumer Agency of Canada) to check whether your driver’s license number has been exposed.
    • If you’ve completed KYC verification with a service, contact its customer support directly to ask about image retention periods and scheduled destruction dates.
    • Avoid reusing copies of your driver’s license for other service sign-ups, and use only single-use links that expire after upload.
    • Pull your credit reports from all three credit bureaus and review them for any unusual inquiry activity over the past 12 months.

    Key Issues at a Glance

    • A single KYC vendor’s breach of 153 million driver’s licenses is a direct consequence of the lack of industry standards.
    • The fact that high-ranking officials’ identities are tied to the same pipeline extends the incident into a national security threat.
    • Even if image disposal obligations are codified into law, no oversight body exists to verify actual compliance.
    • The emergence of dark web self-service search platforms shatters the assumption that “once leaked, the damage is done.”

    Frequently Asked Questions

    How can I check whether my driver’s license has been exposed?

    No official exposure lookup tool has been released yet. The most practical approach is to periodically check for unusual activity through credit bureaus or identity theft monitoring services.

    What kind of damage can be done with just driver’s license information?

    It can be used to bypass identity verification on other services, leading to potential outcomes such as SIM swapping, opening financial accounts, or filing fraudulent tax refund claims.

    Why do KYC vendors keep original IDs for so long?

    It is largely so the data can be used as evidence during re-verification or in dispute resolution. Very few countries have legislated specific retention periods, leaving the matter to industry self-regulation.

    This article is based on KrebsOnSecurity’s original reporting.

    Source Article

    This article was prepared with reference to the following original: Krebs on Security — FBI Probes Service Selling 153M+ Drivers Licenses

  • JFrog Vulnerability 4-Step Audit — Admin Token Theft Just Days After CVE-2026-82329 Patch

    JFrog Vulnerability 4-Step Audit — Admin Token Theft Just Days After CVE-2026-82329 Patch

    Key Summary

    • CVE-2026-82329 is an authentication-bypass vulnerability in JFrog Artifactory, rated critical with a CVSS score of 9.8
    • The flaw enables administrative-level access on default configurations
    • Threat actors began exploiting the vulnerability in real-world attacks within days of patch disclosure, according to watchTowr

    A practitioner’s perspective to help security operators quickly assess the risk of the JFrog Artifactory vulnerability and review their patching, detection, and containment procedures

    Table of Contents

    JFrog vulnerability CVE-2026-82329 admin token theft

    The JFrog vulnerability CVE-2026-82329 was exploited in real-world attacks just days after its patch was disclosed. It is an authentication-bypass flaw that allows an administrative privilege token to be minted on a default-configured Artifactory instance. A CVSS 9.8 rating effectively means “every instance left at default settings is a target.” The watchTowr report featured on The Hacker News explicitly highlighted this time gap.

    What Is the JFrog Vulnerability CVE-2026-82329?

    Artifactory is an artifact repository used by many organizations for software build and distribution. Code, binaries, and container images all converge in one place. Once an attacker gains a foothold, the entire software supply chain is affected.

    This JFrog vulnerability bypasses the authentication layer itself. It means there was a path to mint an administrator token without any credentials. A CVSS 9.8 is an uncommon score: the rating is awarded when network access alone is sufficient to exploit the flaw with no privileges required.

    Default Settings Are the Most Dangerous

    The flaw is exploitable on default configurations. Instances running without hardened authentication, IP restrictions, or a separate gateway are affected as-is. Artifactory operated within internal build pipelines is usually not directly exposed externally, but if a VPN or SSO bypass route exists, the same flaw still applies.

    The Gap Between Patch and Exploitation of the JFrog Vulnerability

    Immediately after the patch was disclosed, watchTowr analyzed that threat actors had begun using this JFrog vulnerability in real attacks. The time from exposure to exploitation keeps shrinking. During the 2021 Microsoft Exchange incident it took several weeks; today it is resolved in a matter of days.

    From a practitioner’s standpoint, the most dangerous aspect of the JFrog vulnerability incident is this time gap. While patch application is pushed to next week’s work, tokens may already have been issued. You need to review logs under the assumption that “it may already be too late,” not merely as a “patch recommendation.” Without that mindset, even after the patch is applied, an intrusion can persist using tokens that were already minted.

    Token Theft Is Not an Isolated Incident

    Around the same time, KrebsOnSecurity reported that the FBI is investigating a case in which 153 million driver’s license records are being sold. There is no direct link, but the same trend is clear: identity and authentication credentials have become the common currency of attack. Admin tokens, session keys, and identity information — these three are now the core resources of the current threat landscape.

    Comparison: Exposure-to-Exploitation Timeline

    Incident Year Exposure → Exploitation
    Microsoft Exchange Proxylogon 2021 About 2–3 weeks
    Log4Shell 2021 About 1–2 weeks
    VMware vCenter 2021 About 3–5 days
    JFrog vulnerability CVE-2026-82329 2026 Within a few days

    As the table shows, the unit of time has shifted from “weeks” to “days” over the past five years. The next shift is likely to “hours.”

    What to Do Right Now

    • Check your Artifactory version and immediately upgrade to the patch version announced by JFrog.
    • Perform a full audit of administrator token issuance logs from the past 30 days to identify any unauthorized token IDs.
    • Verify whether your Artifactory instance is exposed externally and check for any bypass routes outside of VPN/SSO.
    • Add SIEM rules for anomalous administrator login patterns involving unusual IPs, countries, or time zones.
    • Until the emergency patch is applied, restrict access to the admin console to a whitelist of IPs at the WAF/reverse proxy layer.

    Practical Application Points

    One common failure I see in the field is closing out a vulnerability as “resolved” immediately after applying a patch, without auditing tokens. With an incident like this JFrog vulnerability, that attitude itself is risky. The following four items should be elevated in priority.

    • Redefine your patch SLA by severity tier. Establish a principle of applying CVSS 9.0+ within 72 hours.
    • Promote token issuance events on critical infrastructure to real-time alerting.
    • Re-audit the external exposure surface of internal build pipelines every quarter.
    • Run patching and log investigation in parallel, based on the assumption that the exposure-to-exploitation window is shrinking.

    Frequently Asked Questions

    How do I check whether we use Artifactory?

    Check whether the build/CI systems used by your software development teams include Artifactory. A quick way to identify it is to search CI tool configuration files (such as Jenkins or GitLab CI) for the Artifactory domain or repository URL.

    I don’t know the patch version. Where can I check?

    The patch version and download link for CVE-2026-82329 are available in the official JFrog security advisory. First check the current version in the About menu of your instance’s admin console.

    What if an admin token has already been issued?

    Immediately revoke the affected token ID and reissue all credentials for the same account. Simultaneously trace how far that same token was called from build servers, deployment systems, and container registries.

    Is a WAF alone sufficient to block the attack?

    A WAF alone is not enough. It is a temporary mitigation; patch application and token audit are the essential remediation. There is always a possibility that a bypass route will emerge.

    The time from exposure to exploitation is no longer measured in days. The JFrog vulnerability case has compressed that window to hours. It is time to redesign the priority framework for your internal infrastructure around CVSS severity tiers.

    Reference Source

    This article was prepared by verifying the following original source: The Hacker News — Attackers Exploit Critical JFrog Artifactory Flaw to Mint Admin Tokens Days After Disclosure

  • Three Cognitive Biases — How the Trojan Horse and Socrates Proved Humans Are Security’s Weakest Link

    Three Cognitive Biases — How the Trojan Horse and Socrates Proved Humans Are Security’s Weakest Link

    cognitive bias

    Key Summary

    • The second installment of Professor Kim Jeong-deok’s special series, covering the core theme of Part 1, ‘hacking perspectives’
    • Companies pour massive capital into firewalls and multiple layers of advanced security solutions to defend their cyber territory, a period the author calls ‘the era of the most formidable digital walls in history’
    • As technical defenses grow stronger, major security breach incidents paradoxically continue to occur, and the cause lies not in technology but in ‘human psychology and cognitive biases’

    Analysis

    Cognitive bias brings systems down more often than the most expensive piece of security equipment. In 2024 alone, more than 70% of security breach incidents worldwide began with human error or social engineering. Episode 2 of ‘Hacking Security,’ serialized on Boan News, tackles this point head-on. The stronger the technology gets, the more the human becomes the entry point.

    The Trojan Horse and the Lesson of Cognitive Bias

    The Trojan Horse story began after a ten-year siege, when the Greek forces left a giant wooden horse outside the city walls and withdrew. The Trojans brought the offering inside. Tradition tends to emphasize this far, but the more important question is why they brought it in without suspicion.

    What fell here was not a physical fortress. What fell was the gods — that is, trust and loyalty, the reverence owed to a god and an object of worship. The attacker exploited not the city wall but the recipient’s trust structure. Three thousand years later, the structure is the same. Email attachments, phone calls disguised as legitimate contacts, and ransomware masquerading as a trusted tool are all Trojan Horses in the form of an ‘offering.’

    What the author highlights in this example is not the sophistication of the attack. It is the recipient’s decision, rationalized within their own belief system. What stopped the doubt was not technology but perspective.

    Socratic Questions: Conversational Attacks That Target Cognitive Bias

    Socrates kept asking his students endless questions. He never gave answers; instead, he let the other person recognize the logical gaps in their own replies. This dialectic method is a core technique of classical philosophy.

    Yet the same structure is the archetype of social engineering. Attackers stimulate a target’s cognitive bias with questions like ‘Have you ever experienced something like this?’ The user, driven by a desire to help or by deference to authority, hands over information voluntarily. That information is often an account, a card number, or access credentials to an internal system.

    Here is a concrete example. In an attack on a call center employee, the question ‘May I ask you a few questions to verify the customer’s identity?’ is indistinguishable from a normal work process. At the end of that question sits a password. From a practitioner’s perspective, this pattern works more precisely than signature-based detection.

    Hacking Perspectives: The Layer Technology Cannot Reach

    Professor Kim Jeong-deok’s ‘hacking perspectives’ pinpoints this exact issue. Attackers don’t break the code — they change the person’s perspective. This is not a problem of cryptographic algorithms or firewall rules.

    What companies spend on defending their cyber territory grows every year. Despite that, major breach incidents never stop. In an era when even Claude AI accounts are being stolen through infostealers, technology alone cannot provide the answer. This is an era of ‘the most formidable digital walls in history’ and, at the same time, the era in which the most breaches are being recorded. Within it, the cognitive bias of the human resident remains the weakest link.

    Why Human Security Must Be Redesigned in the AI Era

    Generative AI crafts convincing phishing emails in seconds. There are no grammatical errors. It references the target’s job title, department, and recent projects. The speed at which cognitive biases become a target operates on a completely different scale from the past.

    That said, AI is also part of the solution. Behavior-based anomaly detection, user behavior analytics, and short micro-trainings at the moment of decision can supplement human cognition. Yet technology cannot replace cognitive bias. It is only an auxiliary tool.

    What to Do Right Now

    • Hold links in emails and messages from unclear sources for 24 hours, then reconsider whether to click.
    • Establish a team rule that ‘urgent’ requests from someone in authority must be verified once more through a separate channel (phone, in person).
    • If you are asked for identity verification or payment information, hang up on any channel and call back through the official main number.
    • Run a team-wide phishing simulation once a month, and share click-through rates and reporting rates as KPIs.
    • Place a note by your desk that says, ‘If someone asks for it, I do not give it.’

    Key Issues at a Glance

    Responding to perspective hacking starts with culture design, not tool adoption. The Trojan Horse recipient did not fail to know the danger — it was a belief system that did not question the offering’s identity that allowed the infiltration to pass. The same structure operates today at the very front line of decisions: internal rules, payment approval procedures, and trust placed in external contacts.

    • The 10-second rule before deciding: For every external request, ask yourself, ‘Can I push this decision back by 10 seconds?’
    • Role-based permission redesign: Structure access so that two or more people must approve before the same information is exposed, reducing individual bias.
    • Cognitive bias branch training: Train with cases around three biases — confirmation bias, authority bias, and urgency bias.

    Frequently Asked Questions

    You say cognitive bias is the biggest vulnerability in cybersecurity — is the human problem really larger than the technology problem?

    Industry statistics for 2024 show that more than 70% of major breach incidents began with human error or social engineering. That is higher than the proportion of technical flaws. Attacks that bypass human cognition also slip past signature-based detection more easily.

    Does the Trojan Horse example still apply to security today?

    The form is different, but the essence is the same. Attachments, phone calls disguised as legitimate contacts, and ransomware masquerading as a trusted tool are all Trojan Horses in the form of an offering. The structure of attacking the recipient’s trust is no different from 3,000 years ago.

    AI has made social engineering more sophisticated — how should an ordinary office worker prepare?

    Shifting your default stance from ‘trust’ to ‘verify’ is the starting point. Assume that any request for identity verification, payment, or a password is fraudulent by default, and confirm through an official channel. That habit alone reduces significant risk.

    What does the Socratic method have to do with attack techniques?

    Socrates used questions to let the other person recognize their own logical gaps. Attackers use the same structure to stimulate the target’s psychological gaps and induce voluntary information disclosure. It is the archetype of conversational design that creates cognitive bias.

    Ultimately, the strongest line of defense is not in the code. It lies in the user’s awareness and judgment. What the Trojan Horse demonstrated, and what the Socratic method has repeated for more than 2,400 years, is that the human mind is both the most sophisticated channel and the most decisive vulnerability. Advanced security solutions must be redesigned from the starting point of acknowledging this fact. Cognitive bias is a weakness, but once recognized, it becomes the most powerful first line of defense.

  • 5 Lessons from the Berlin Ransomware Attack — What the Rhysida Breach Means for Public Institutions

    5 Lessons from the Berlin Ransomware Attack — What the Rhysida Breach Means for Public Institutions

    Berlin Ransomware

    Key Summary

    • The Berlin city government officially confirmed that the Rhysida ransomware gang posted a confession on a dark web leak site and is now attempting financial extortion against the city
    • Attackers gained initial access weeks before being detected and performed lateral movement across parts of Berlin’s administrative network, according to the investigation
    • Exposed data is believed to include personnel records, citizen service information, and internal financial records; the full scope of the breach remains under forensic investigation

    Analysis

    The Berlin ransomware incident is not just a simple hacking case. The Berlin city government officially confirmed that the Rhysida gang posted a confession on a dark web leak site and is now attempting financial extortion. Weeks before detection, the attackers had already completed lateral movement across sections of Berlin’s administrative network.

    This is the most painful point from a practitioner’s perspective. The fact that a city-scale administrative network failed to detect external intruders for weeks means that internal visibility and anomaly detection systems were not properly in place.

    Berlin Ransomware Breach Timeline — From Initial Access to Data Exfiltration

    According to the Berlin city government’s announcement, the attack followed a typical ransomware intrusion pattern. Initial entry is believed to have come through phishing emails, exposed VPN/RDP endpoints, or external Initial Access Brokers (IABs). This was followed by a double-extortion tactic: abusing legitimate cloud services (remote management tools, file sharing) to exfiltrate data, and then deploying bulk encryption at the end.

    According to BleepingComputer’s report, the leak site is believed to include personnel records, citizen service information, and internal financial records. The exact scope of the breach will be confirmed by the forensic investigation at Berlin’s IT Coordination Office (ITDZ Berlin).

    The Rhysida Gang’s RaaS Structure and Tactics

    Rhysida is a Ransomware-as-a-Service (RaaS) operation that first appeared in 2023. Core operators provide the ransomware builder and leak site infrastructure, while affiliate attackers use these tools to perform their own intrusions. The profit split between attackers and operators is typically known to be around 7:3 to 8:2.

    Rhysida’s weapon is its consistent target selection across healthcare, government, education, and manufacturing sectors. Ransoms are typically set in the seven-figure dollar range, and if unpaid, the leaked data is released in stages to apply pressure. The fact that the Berlin ransomware incident followed the same pattern confirms that the gang’s operational playbook works just as well against public institutions.

    Primary and Secondary Damage Scenarios

    Exposed personnel and financial data immediately becomes phishing fodder. An attacker who knows employee names and internal report titles can craft a convincing email disguised as a “security check notice.” Under GDPR, the city of Berlin has notified the relevant supervisory authority of the breach, but the real danger concentrates in the days immediately following notification. This is because secondary phishing attacks, crafted from the externally exposed information, will target both city employees and citizens at the same time.

    What I consider the most serious aspect of this incident is the length of the compromise period. The fact that lateral movement was possible for weeks strongly suggests that the attacker obtained domain controller privileges.

    Incident Response — ITDZ Berlin’s 7-Day Sprint

    The city of Berlin is simultaneously working with external incident response teams on the following tasks: blocking intrusion paths, bulk revoking compromised credentials, auditing access paths, and collecting forensic evidence. The city’s data protection authority is gradually disclosing the scope of the exposed information to citizens.

    The GDPR notification obligation is 72 hours, but full response completion can take several months. Looking at similar European public institution cases, some have taken 4 to 6 months just to recover their administrative networks.

    5 Lessons from the Berlin Ransomware Incident for Public Institutions

    The Berlin ransomware case vividly demonstrates what risks city-scale infrastructure faces. Compared to U.S. city government breach cases, the initial intrusion vectors are strikingly identical: unpatched VPN/RDP gateways, reused service account passwords, and SIEMs with anomaly alerts turned off.

    In a similar context, as seen in the article China Hacking Correction: Words Reversed in Just 3 Days, cyberattack incidents often see the truth shift during the post-incident reporting process. The final damage scale of the Berlin ransomware case could also vary significantly based on forensic investigation results.

    Key Issues

    The Berlin ransomware incident raises three core issues.

    First, weeks of detection failure exposes the limitations of public institution SIEMs. Second, VPN/RDP patching cycles are slower than attackers’. Third, double extortion must now be assumed as the baseline scenario for public institutions.

    What to Do Right Now

    • Extract the list of externally exposed VPN/RDP gateways today and compare them against patched versions
    • Audit whether administrator account passwords are being reused and immediately rotate domain controller credentials
    • Verify that SIEM anomaly detection rules are enabled and add Indicators of Compromise (IoC) feed sources
    • Verify that backup data is stored separately in offline, immutable storage
    • Run at least one secondary phishing simulation drill for employees within this week

    Frequently Asked Questions

    What is Rhysida ransomware?

    It is a RaaS-type ransomware gang that appeared in 2023, primarily active in healthcare, government, and education sectors. It mainly uses double-extortion tactics, and ransoms are typically set in the seven-figure dollar range.

    Did the Berlin city government pay the ransom?

    The Berlin city government’s official position is refusal to negotiate. In general, public institutions have a strong tendency to decide not to pay ransoms.

    How is the leaked citizen information being protected?

    Berlin’s data protection authority is currently analyzing the scope of the leak, and citizens will be notified in stages. Under GDPR, the supervisory authority was notified within 72 hours.

    Could the same thing happen to Korean public institutions?

    Yes, the same initial intrusion vectors exist in Korea. VPN patch delays and credential reuse are common issues across global public institutions.

    The Berlin ransomware case ultimately demonstrates the structural vulnerabilities of public sector cybersecurity. The scarier fact isn’t the intrusion itself, but that it went undetected for weeks. Even after the external incident response team completes intrusion blocking and credential revocation, the secondary phishing risk will persist for at least a quarter. Operations teams must keep this in mind.