SOCLYDE logo
Current languageEN
Cybersecurity newsCybersecurityData breachSecurity advisory

Denmark: unauthorized access to CPR records

Unauthorized parties accessed CPR data by misusing a private company’s legitimate lookup access. What authorities disclosed and what people can do next.

Published on · Updated on

By Soclyde Team

Unidentified administrative forms are reviewed on a desk

In summary

  • Denmark reported unauthorized CPR register access, detected on October 2 after large-scale queries in September.
  • The alleged attacker claims to have used a former employee’s 123456 password; that explanation has not been officially confirmed.
  • Verify unexpected requests through official channels and never share a password or one-time code with an unsolicited caller.

Explore next

Soclyde resources

Article contents

On October 5, Denmark’s ministry disclosed unauthorized access to information in the Central Person Register (CPR). Authorities say unauthorized parties used a private company’s lawful access to make large-scale queries during September; the ministry says it detected the issue on October 2.

What authorities established

Authorities refer to about 8.8 million records, including people who have died or emigrated. CPR data can include an identification number, name and address. Protected addresses are reportedly outside the disclosed scope. The figure counts records, not necessarily current residents.

Legitimate access used improperly

The disclosure concerns unauthorized parties misusing a private company’s lawful register access, rather than a claimed technical intrusion into CPR infrastructure. That distinction matters: access logs, permissions and usage controls are central to the investigation. Authorities have not publicly attributed the activity to a criminal group.

What has been reported about the “123456” password

In its incident timeline, CSIS reports that an alleged attacker told Politiken on October 8, 2026 that they had used a former employee’s “123456” password. CSIS notes that this claim has not been officially confirmed. The password should therefore not be presented as the established cause of the CPR incident.

CSIS also highlights a detection problem: the large-scale queries were reportedly identified through an unusual invoice rather than security monitoring. Password choice alone does not cover all the controls that need to be examined around this third-party access.

Why this data creates lasting exposure

A national identifier cannot be replaced like a password. Paired with a name and address, it can make phishing or impersonation more convincing. Authorities have not said that every record was copied or that fraud has occurred; observed access and later misuse should remain distinct.

Steps for people who may be affected

Be cautious of a call or message that cites your address or CPR number to pressure you into clicking, paying or confirming a secret. Verify requests through the organization’s official contact details. Never share a one-time code or password with an unsolicited caller.

What businesses should check

For a small business, the CPR case is a reason to review access entrusted to a provider, particularly access to customer files or business applications. DI Digital recommends checking who can use CPR access and whether an unusual volume of queries would be detected. Apply that review to external accounts that can view or export your own data:

  • identify each provider account, its owner and the data it can access;
  • remove accounts that are no longer needed in each service, particularly after an employee leaves or a contract ends;
  • use unique secrets and enable multifactor authentication where the service supports it;
  • have the service administrator review logs and alerts for unusual queries or exports.

The CPR case also underlines why a name and a national identifier are not enough to prove identity. Before resetting a password or a second factor, verify the request through an independent channel. Our SMB password policy guide helps assign these responsibilities.

How this relates to Soclyde

Soclyde does not control CPR access and cannot reverse this exposure. For accounts you manage, an encrypted vault can reduce password reuse and scattered secret sharing. This complements identity controls and the authorities’ response; it does not protect register data.

Key points

Keep the disclosed scope in view, while distinguishing observed access from confirmed misuse. Follow official updates and apply the steps relevant to your accounts. For team secrets, see our secure password sharing guide or contact Soclyde.

Frequently asked questions

Was the CPR register hacked?

Authorities described misuse of a private company’s lawful register access. They have not announced a technical intrusion into CPR infrastructure. The alleged attacker claims to have used a former employee’s 123456 password; according to CSIS, that explanation has not been officially confirmed.

What data is involved?

The disclosed scope may include CPR number, name and address for about 8.8 million records. Protected addresses are reportedly excluded; follow official updates.

What should I do if contacted?

Do not click or share a code. Contact the organization through its official website and report suspicious messages to the relevant authorities.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading