South Korean retailer Coupang disclosed in December 2025 that a former employee used a stolen electronic signing and authentication key to reach data on 33.7 million customers. The access ran from June to November 2025, roughly five months. The company's chief executive resigned that December.
What is going on
Most websites do not check your password on every click. After you log in, the site hands your browser a signed token, and that signature proves the token is genuine.
The signature is made with a secret signing key held by the company. Think of it as the stamp a hotel uses to make room keycards. Whoever holds the stamp can make a card for any room, without ever visiting the front desk.
In the Coupang data breach, a former employee had that stamp. Because the key was still valid long after the person left, the access looked legitimate to the systems checking it.
Who is affected
Coupang customers are affected directly. But the pattern is not specific to one retailer or one piece of software.
Any business whose login tokens are signed with long-lived keys that staff or contractors can read faces the same risk after someone departs. That includes custom web apps, API keys shared with developers, mobile app back ends and self-hosted platforms where the key sits in a config file or an environment variable that several people have seen.
What to do now
- Rotate signing keys whenever staff or contractors leave. Treat it as part of offboarding, alongside disabling the email account.
- Move keys into a secrets manager or hardware security module (HSM). These store the key so applications can use it without any person being able to copy it.
- Write down who holds which key. You cannot rotate a secret you have forgotten about.
- Alert on tokens issued outside normal flows. A valid session that never passed through your login page is a strong warning sign.
- Keep access logs for months, not days. This access lasted five months; short log retention would have hidden most of it.
How to check your own site
A scan cannot see a key an ex-employee copied, but it can find the careless exposure that often leaks one. The free Website Security Check flags outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want to go further on a site you own and have verified, you can run a full scan, which adds active OWASP Top 10 testing, port and service checks with CVE matching, WordPress and Magento deep scans, and checks for exposed files and secrets left in public places.
Source: Coupang, December 2025.
Comments
No comments yet.