
Passkeys: what Denmark's “123456” password leak teaches SMEs

In Denmark, the password “123456” opened access to the data of 8.8 million people. What passkeys change for your SME's website and business tools.
In early October, Denmark learned that an outsider had obtained the names, addresses and personal identification numbers (the CPR number) of around 8.8 million people. They did not break into a government system. They signed in with the credentials of a small company in Odense which had, quite legally, the right to query that register.
A few days later, the Danish press revealed the detail that went round social media: at least three of the company's accounts, including the administrator account, used the password “123456”. In the middle of Cybermois, the cybersecurity awareness month, the story speaks to any SME manager. It also raises a very concrete question for your company's website or app: should you still be asking your customers and your teams for passwords?
What we know about the Danish leak
The Danish ministry responsible for digital affairs announced the incident on 5 October 2026 in an official press release. The register's administration had spotted, on the evening of Friday 2 October, unusual activity that took place in September. The misused access belonged to a private company authorised to consult the register. It was cut off, the Danish data protection authority was notified and the police are investigating.
The broadcaster TV 2 then identified the company: Pays ApS, a firm in Odense with only two employees according to the Danish business register. Its manager confirmed that its legitimate access had been used by someone else. More than 14 million searches were run in about ten days. The most striking part is how the alarm was raised: an official at the register found the company's invoice unusually high.
On 9 October, the daily newspaper Politiken published its analysis: at least three of the company's profiles used “123456”, including the administrator account. Straight afterwards, according to DR, the register's administration wrote to the 1,039 companies that have access to it to remind them of the rules. Each one must have a person responsible for security, regularly check its employees' access and monitor the number of look-ups every month.
Why one weak password is enough to open everything
You might think this is a blatant mistake that only happens to others. Yet this kind of situation is more common than you would imagine in a small organisation: one account shared between three colleagues, a former employee's access that was never closed, the same password reused across several tools because it is more convenient.
The root of the problem lies in what a password is. It is a secret the user knows and the server must be able to check. So it can be guessed, reused, typed into a fake sign-in page or found in an old leak. The more accounts your company has, the greater the risk, and an SME does not always have someone whose job it is to keep an eye on all of this.
Two-factor authentication by SMS clearly reduces the risk, and it is always better than nothing. An SMS code can still be intercepted, or coaxed out of you by a fake adviser on the phone. This is where passkeys become interesting.
Passkeys, explained without jargon
A passkey replaces the password with a pair of cryptographic keys. The FIDO Alliance, the consortium behind this standard, describes it as a credential stored on your phone, your computer or a physical security key. To sign in, you make the same gesture as when you unlock the device: your fingerprint, your face or your PIN.
The private key stays on the user's device. The website only keeps the public key, which cannot be used to sign in on its own. If your website's database ever leaks, there is therefore no password to recover. And since each passkey is tied to the exact address of the website, a fake sign-in page cannot use it.
There are two families. Synced passkeys move from one device to another through the user's manager (iCloud Keychain, Google's password manager or a tool such as 1Password). Device-bound passkeys never leave the device, for example when they are stored on a USB security key. All of them rely on the open FIDO2 and WebAuthn standards, which the main operating systems and browsers already support.
What the CNIL says
In France, the CNIL (the French data protection authority) adopted on 20 March 2025 a recommendation on multi-factor authentication, with a definition of passkeys in an appendix. Its position is nuanced, and it is worth knowing before choosing a solution. Here is what the text of the recommendation says:
“Cryptographically strong authentication is not necessarily multi-factor. This is notably the case for solutions involving a software passkey.” (our translation)
In other words, a passkey protects very well against the theft and reuse of passwords. For it to count as multi-factor authentication, the CNIL states that it must be tied to a specific device and locked with a PIN. Conversely, a password followed by a code received by SMS is indeed multi-factor, without being cryptographically strong. For a standard customer area, a passkey is already a big step forward. For administrative access or sensitive data, we aim for a device-bound passkey, or we add a second check.
What it changes for your company's website or app
Offering passkeys does not mean removing passwords overnight. On a custom project, we add them alongside the existing sign-in, then let users switch over at their own pace.
A customer area or a mobile app
This is the easiest case to justify. Your customers sign in with their fingerprint or their face, with no password to remember or reset. On a website, we rely on the browsers' WebAuthn API. In an iOS or Android app, on the features provided by the system. The longest part is not the code. It is getting the user journey right, so that people understand what they are being offered when they create their key. If the app is still to be built, our article on the cost of a mobile app in Switzerland helps you plan this kind of feature in the budget.
A business tool or a back office
For your teams, the benefit is even clearer. An administrator account protected by a device-bound passkey is exactly the lock the Danish company was missing. It is also a good time to tidy up: one named account per person, rights limited to what each person needs, and access closed on the very day someone leaves.
Account recovery, the point people forget
A phone gets lost, a computer gets replaced. You need to plan how someone regains access without reopening a back door. If recovery relies on a simple link sent by email, all the security of the passkey depends on the mailbox. For sensitive accounts, we recommend registering at least two passkeys (on the phone and on the computer, for example) and keeping a fallback procedure checked by a person.
That is also why we look at the whole chain, right down to the hosting and deployment of your projects, and not just the sign-in screen.
What you can do this week
No need to wait for a redesign. Here are the checks we would do first:
- List the accounts with administrator rights on your website, your email, your CRM and your business tools, then close the ones no longer in use.
- Turn on passkeys wherever your providers already offer them, starting with email and administrator accounts.
- Reject the most common passwords in your own applications. Current libraries can do this without much difficulty.
- Set up an alert for abnormal volumes of sign-ins, exports or look-ups. In Denmark, it was an invoice that raised the alarm, more than ten days after the searches ended.
- Ask your providers how they protect their own access to your systems.
This last point ties in with what we explained about the attack on supermarkets' connected fridges: your security also depends on that of the companies you open the door to.
If you are preparing a customer area or an internal tool, passkey sign-in should be planned from the design stage. Planned from the start, it fits easily into the budget for custom software. Added afterwards, it often means reworking account management.
Key takeaways
The Danish leak did not come from a sophisticated attack. It came from a password anyone could have guessed, on the account of a very small company that had very broad access. Passkeys remove that weak link: there is no longer a secret to guess or anything to steal from your database, and your users sign in faster. The CNIL recognises their strength, while specifying the cases where you need to go further.
Want to know where your website's or app's logins stand? We are in Rumilly, near Annecy, and we are happy to talk it through, by video call or over a coffee, without jargon.
Security updates for your website or app are part of our maintenance service.
Frequently asked questions
What is a passkey?
It is a sign-in credential that replaces the password. It relies on a pair of cryptographic keys: the private key stays on your phone, your computer or a security key, and the website only keeps the public key. You sign in with the same gesture you use to unlock your device, such as your fingerprint, your face or a PIN.
Is a passkey safer than a password with an SMS code?
Against phishing and database theft, yes: there is no secret to type into a fake page or to steal from the server. The CNIL adds a nuance. A passkey is cryptographically strong authentication, but it only becomes multi-factor if it is tied to a specific device and protected by a PIN.
What happened in Denmark with the password “123456”?
In early October 2026, the Danish authorities announced that the names, addresses and CPR numbers of around 8.8 million people had been obtained by misusing the legitimate access of a small company in Odense, Pays ApS. According to the daily newspaper Politiken, at least three of the company's accounts, including the administrator account, used the password “123456”.
Can passkeys be added to an existing website or app?
Yes. On a website, we use the browsers' WebAuthn API, and in a mobile app the features provided by iOS and Android. They are usually offered alongside the existing sign-in, with a solid procedure for recovering an account when a device is lost.
How can METEORA help my business secure its logins?
We start by reviewing the accounts and logins of your website, your app and your business tools. Then we suggest the priority fixes, which can range from tidying up accounts to adding passkeys to a customer area or a back office. We are based in Rumilly, near Annecy.
How much would your project cost?
Project type, features, timeline: a costed estimate in two minutes, with no commitment.
Are your logins really protected?
From Rumilly, near Annecy, we review the logins of your website, your app and your business tools, then tell you plainly what needs fixing first.