Denmark’s government disclosed that hackers stole roughly 8 million records from the country’s Central Person Register (CPR), including names, addresses and state-issued ID numbers. The access happened in September 2026 and was discovered on October 2. Officials say the attackers abused a Danish company’s lawful access to search the register, which makes this a third-party access problem as much as a hacking story. Any business that connects to a government or partner database should review who can query what, how much, and how quickly anyone would notice.
What was stolen
The Danish government said this week that attackers obtained about 8 million records from the Central Person Register, known by its Danish abbreviation CPR. As TechCrunch reported on October 5, the stolen data includes names, addresses and state-issued identity numbers. The affected records cover people who live abroad and people who have died, and some date back decades.
The scale looks odd at first glance, since Denmark has a population of roughly 6 million. The explanation is in what the register holds. The CPR contains around 11 million records in total because it keeps entries for former residents and the deceased as well as current citizens. The 8 million figure therefore represents a large majority of the whole register rather than more people than exist.
Danish minister Christina Egelund described the incident as a “serious incident.” Officials consider it the largest data breach in Danish history. The government has not said who is responsible.
What the CPR is, and why it matters
Many countries have a national population register, but Denmark’s is unusually central to daily life. The CPR number, a personal identity number assigned at birth or on registration, is used across the public sector for taxes, health care and benefits, and it is widely used in the private sector to identify customers. Banks, insurers, employers and utilities all rely on it in some form.
That design has real benefits. It makes administration efficient and lets organisations verify identity without long forms. But it also means the identifier is both an index key and, in practice, a partial credential. A leaked CPR record is not like a leaked password, which can be changed in minutes. An identity number issued for life cannot easily be revoked, so a breach of this kind creates risk that lasts for decades.
TechCrunch noted parallels with attacks on other national identity databases, including a 2016 breach in Turkey and several exposures of India’s Aadhaar system. The recurring lesson in those cases is that a database built to make identity checks easy is, for the same reason, valuable to anyone who wants to impersonate people.
How the attack worked
The most important detail is the method. According to Danish authorities, the hackers exploited “a Danish company’s lawful access to search for information in the CPR system.” In other words, the attackers did not necessarily break into the register’s core systems. They used a route the system already allowed: a company with legitimate permission to look up citizens.
Some Danish companies are authorised to query the CPR for legitimate purposes such as verifying customer details. That access is a normal part of how the system works. But it creates a chain of trust. The security of the register is only as strong as the security of every organisation with a connection to it. If an attacker compromises one authorised party and the register’s controls do not notice unusual behaviour, the attacker inherits that party’s privileges.
The timeline raises a second question. The unauthorised access took place in September 2026, but it was not discovered until October 2. That is a gap of days to weeks in which a very large volume of data could be extracted. Extracting millions of records through a search interface is not a subtle activity. It involves a very large number of queries, usually far above the normal pattern for any legitimate user. Whether the volume of lookups was flagged, throttled or noticed earlier is a question Danish authorities will probably be asked.
Why third-party access is the weak point
The Danish case fits a pattern security teams have worried about for years. Large organisations often harden their own perimeter while giving partners, suppliers and customers privileged access to sensitive systems. Those partners may have weaker controls, less monitoring and fewer staff dedicated to security. Attackers know this and target the weakest link.
There are several reasons the problem persists. Access is granted for good business reasons and rarely reviewed afterwards, so permissions accumulate. The partner’s credentials may be shared among staff or embedded in software. Rate limits are set generously because the legitimate use cases are varied. And because the access is “lawful,” its use rarely triggers the alarms designed to catch unauthorised users.
The outcome, in this case, was that one authorised connection appears to have been enough to reach most of a national register. That is the definition of excessive blast radius: the damage a single compromised account can cause is far larger than the legitimate task it was meant to perform.
What this means for businesses
Companies do not need to be a national government to learn from this. Any business that exposes an API, a lookup service or a data feed to partners is in the same position on a smaller scale. A practical review should cover at least the following.
Limit what each account can do
Apply the principle of least privilege to partner accounts. If a client needs to verify one customer at a time, it should not be able to retrieve millions of records. Restrict the fields returned, so that a verification check returns a yes or no rather than a full personal profile whenever possible.
Rate-limit and alert on volume
Set quotas that reflect realistic use, and trigger alerts when a partner exceeds them. A sudden spike in queries from an account that normally makes a handful a day is a strong signal of compromise. Alerts need an owner who will act on them quickly, not just a dashboard.
Review third-party access regularly
Keep an inventory of who has access to what, and recertify it at least annually. Remove access that is no longer needed. Require partners to meet security standards, such as multi-factor authentication and credential rotation, as a condition of connection, and verify rather than assume.
Prepare for a persistent-identifier leak
If your business uses a national ID number as a customer identifier, assume it may be exposed. Do not treat it as a secret. Add independent verification steps for sensitive actions such as changing an account, opening credit or resetting access, and train staff to expect impersonation attempts that use accurate personal details.
Know your notification duties
For organisations covered by the EU’s General Data Protection Regulation, a personal data breach generally has to be reported to the supervisory authority within 72 hours of becoming aware of it, where feasible, and to affected individuals when the risk to them is high. Having a tested incident-response plan, with legal and communications roles defined in advance, makes the difference between a controlled response and a chaotic one.
What individuals should do
For people in Denmark, and for Danes living abroad, the main risk is not immediate account takeover but targeted fraud. Accurate names, addresses and ID numbers make phishing messages and impersonation calls more convincing. Reasonable precautions include treating unexpected messages that cite personal details with suspicion, avoiding sharing codes or approving login prompts you did not initiate, and watching official government channels for guidance. Checking credit reports for unfamiliar activity is sensible, and so is asking institutions how they verify identity for sensitive requests.
Families of deceased people are also affected, since deceased records were included. Identity theft involving the dead is a known fraud category, partly because it can go unnoticed for a long time.
The policy questions ahead
The breach will probably prompt debate in Denmark and beyond about three issues. The first is access: whether so many private companies need direct lookup rights to a register of this sensitivity, and whether tighter tiers of access are needed. The second is detection: how a theft of this size could continue for as long as it did before discovery. The third is design: whether national identity numbers should continue to serve as a universal key across public and private systems, or whether systems should move toward separate, revocable identifiers.
None of these questions has a simple answer. Convenience and security pull in opposite directions, and a system that works well for administration is often fragile against abuse. But the scale of this incident makes it hard to argue that the current balance is correct.
Bottom line
The theft of about 8 million records from Denmark’s CPR is a serious incident in its own right, and it is also a useful case study. Attackers reached sensitive data by using access that was supposed to be legitimate, and the theft went unnoticed for some time. For businesses, the practical takeaways are to shrink the privileges of every connected party, watch volumes as closely as credentials, and plan on the assumption that a persistent identifier will eventually leak. For governments, the harder task is to rethink how widely a single, permanent ID number should be trusted.
Sources: TechCrunch. Details are as reported on October 5, 2026 and may change as the investigation continues. General information, not legal advice.
Discover more from Kurums | Business Intelligence
Subscribe to get the latest posts sent to your email.