Sourcenext Data Breach: 22.5 Million Records Exposed — What Happened and What to Do Now

A Japanese software company that literally sells security products just announced that attackers walked off with up to 22.5 million of its customers’ records — passwords included. The Sourcenext data breach, disclosed on October 15, 2026, is one of the biggest credential leaks of the year, and it is a brutal reminder of why reusing the same password everywhere is a bet you will eventually lose. Here is what actually happened, what got exposed, and the five things I would do today if any of my accounts were in the blast radius.

What Happened: The Sourcenext Breach, Explained

Sourcenext is a Japanese PC software maker you have probably never heard of unless you follow the Japanese tech market — it is best known for the PocketTalk translator device and its own line of security software, and it trades in Tokyo under 4344.T. On October 15, the company disclosed that its member-information management system had been hit by unauthorized third-party access, potentially exposing up to 22,519,960 customer records.

The timeline is the part that stings. According to the company’s announcement, the unauthorized access began around 10:00 a.m. on October 9. Nobody noticed for four days. An employee finally spotted the anomaly around 9:00 a.m. on October 13, and emergency measures to block the unauthorized external communication were completed by 1:36 p.m. that same day. The company says no further unauthorized access has been confirmed since.

The attack vector was an exploited API — the programming interface the company uses to retrieve member information. In plain English: attackers found a door in the software’s plumbing that was supposed to serve up customer records only to authorized systems, and they helped themselves. API abuse is one of the most common breach patterns in 2026, precisely because APIs sit between everything and are easy to under-protect.

What Data Was Exposed (and the One Thing That Wasn’t)

The reported scope of the Sourcenext data leak is ugly. The potentially exposed fields include names, email addresses, and password combinations, plus home addresses and phone numbers. Depending on each user’s registration status, the leak may also include phonetic name readings, gender, fax numbers, dates of birth, company names, job titles, department names, subscribed services, and registration and login dates. Not every field was compromised for every user — but email-plus-password pairs are the crown jewels here, and they are squarely in the mix.

Why does that specific combination matter so much? Because of credential stuffing. Attackers take leaked email-and-password pairs and spray them at Gmail, Amazon, banks, PayPal, and every other login page on the internet, betting that a meaningful percentage of people reused the same credentials. They are usually right. A breach of one obscure software vendor becomes a breach of your bank account the moment you reused that password.

There is one genuine piece of good news: Sourcenext says credit card information was not stored on the affected system, so payment data is not part of this breach. That is the silver lining. The cloud is that everything else an identity thief needs to impersonate you — name, address, phone, date of birth — may well be out there.

One important caveat: the company frames the figure as “up to” 22.5 million records “potentially” exposed, and the investigation is ongoing. The final confirmed number may land lower. But when a company forces password resets for all affected users — which Sourcenext is doing — you should treat it as real until proven otherwise.

The Irony Nobody Missed

Here is the part of the story doing the rounds in the Japanese tech press: Sourcenext sells security software. A security vendor got breached through an API. It is the locksmith getting robbed, and yes, the jokes write themselves.

But the real lesson is not “even security companies are incompetent” — it is that no company is breach-proof. Not the one selling you antivirus, not your bank, not the social network with a thousand engineers. If your entire security posture is “I trust Company X with my one password,” you are one API flaw away from a very bad week. The people who shrug at breach headlines are the ones who built their defenses assuming breaches happen: unique passwords everywhere, a password manager holding them, and two-factor authentication on the accounts that matter.

5 Things to Do Right Now

You do not need to be a Sourcenext customer for this to apply — treat this as your general breach-response checklist, because the next 22-million-record headline is always closer than you think.

1. Change your Sourcenext password — and everywhere you reused it. The company is requiring password resets for affected users, so do that first. Then comes the harder part: if you used that same password on any other site, change it there too. Every single one. Attackers count on you skipping this step.

2. Stop reusing passwords, starting today. This is the single highest-leverage security habit there is. Every account gets its own random password, full stop. If that sounds impossible to remember, that is because it is — which is why step 3 exists. And if you need a strong one right now, I keep a free password generator on this site that creates cryptographically random passwords in your browser — nothing ever leaves your device.

3. Get a password manager. A manager like Bitwarden or 1Password remembers hundreds of unique passwords so you do not have to — you just remember one strong master password. I compared the big three in detail in my Bitwarden vs 1Password vs Dashlane breakdown if you want help picking one.

4. Turn on two-factor authentication, starting with your email. Your email is the master key to everything — password resets for your bank, your shopping accounts, your social media all flow through it. If an attacker gets your email, they get everything downstream. App-based authenticator codes beat SMS codes, but SMS beats nothing.

5. Watch for phishing wearing a Sourcenext costume. Breach data is phishing fuel. Expect convincing emails about “your Sourcenext account” with urgent links. Do not click links in breach-notification emails — go to the company’s site directly by typing the address yourself. Real companies will never ask for your password over email.

How to Check If Your Info Was in the Leak

The fastest free check is Have I Been Pwned, Troy Hunt’s long-running breach-notification service. Type in your email address and it tells you which known breaches include it, plus which data classes were exposed. It is the first thing I check whenever a breach this size breaks.

One realistic expectation: it takes time for new breaches to be verified and loaded into the database, so if the Sourcenext breach does not show up today, check again in a few weeks. And while you are there, sign up for its free notification service — it will email you the next time your address appears in a breach, which beats finding out from a headline.

Why API Breaches Keep Happening

Quick detour for the curious, because “exploited an API” deserves thirty seconds of explanation. An API is how software components talk to each other — your phone app asking a server “show me my account,” that sort of thing. When an API that returns member records lacks proper authorization checks, anyone who discovers its address can start pulling records at machine speed. That appears to be roughly what happened here: four days of undetected access is consistent with automated harvesting, not someone clicking around manually.

For developers reading this, the fix is boring and well-documented: authenticate every API caller, authorize every request against that specific user’s data, rate-limit aggressively, and log everything so four days becomes four minutes. For everyone else, the takeaway is simpler — you cannot fix companies’ APIs, but you can make sure a breach of Company A never becomes a breach of your bank. Unique passwords do that.

The Bottom Line

Up to 22.5 million records, passwords included, from a company that sells security software. The Sourcenext data breach will not be the last headline like this in 2026 — the only question is whether the next one affects you, and whether you will care when it does.

My honest take: breaches are background noise now. The people who sleep well through them are not the ones with the cleverest single password — they are the ones with a different random password on every site, a manager holding the keys, and two-factor on their email. Set that up once, and the next 22-million-record headline becomes someone else’s problem. Start with a fresh password from our free password generator and go from there.

One comment

Leave a Reply

Your email address will not be published. Required fields are marked *