Welcome Savings Bank Breach: Up to 2,200 Corporate Contact Records Leaked (2026)

Welcome Savings Bank found evidence of a leak during a security review on 3 October. Up to 2,200 corporate contact records, and the fraud they enable.

Ahsan Luqman
Ahsan Luqman
·9 min read·
Welcome Savings Bank Breach: Up to 2,200 Corporate Contact Records Leaked (2026)

Welcome Savings Bank found evidence that corporate client information leaked out of the company, and reported it to financial regulators on 4 October. As many as 2,200 records have been identified so far.

Corporate names. The names of the company contacts. Email addresses. Phone numbers. That is the full leaked list, per the Seoul Economic Daily report on the disclosure. No passwords, no account numbers, no national ID numbers. It sounds like the mild end of a breach. It is not. A name, a work email, and a direct phone number, attached to a company name and a banking relationship, is a complete kit for impersonating the people who move the money.

Two days in, little is confirmed#

The facts are thin and the bank is not pretending otherwise. Welcome Savings Bank found the evidence during an internal security review on 3 October and reported it to regulators the next day, according to the Seoul Economic Daily account. The data is "believed to have been exposed", which is the bank's current assessment, not a final audit. The bank has launched an investigation into how the hacking occurred and the true scope and scale of the leak.

Note the word "believed". Two days after discovery, nobody knows the final number, the entry point, or whether the 2,200 records found so far are the whole story. The bank deserves credit for the speed: it found the evidence on the 3rd and reported to regulators on the 4th. Speed and certainty are different things. Everything below that is not marked as confirmed is the shape of what usually follows this kind of data, not a report of what has already happened.

One more thing about the source. This is a single English report, and the page notes it was AI-translated from Korean. The bank's own notice, if one is public yet, is not in English that I could find this run. Treat quoted phrasing as approximate.

This is not a spam list. It is a fraud kit.#

Retail breaches leak consumers; this one leaked roles. The record says who handles the company's business at Welcome Savings Bank, what they are called, and how to reach them directly. That is the raw material for business email compromise, and it is worth walking through how it gets used, because the fraud looks nothing like spam.

The classic move is the invoice switch, and this dataset is built for it. A supplier's finance team gets an email from their customer's accounts contact. The name is right. The company is right. The banking relationship is real, which the attacker knows from the leaked records. The email says the company's settlement account changed and the next invoice should go to the new one. Nothing about the message looks wrong except the destination of the money, and finance teams process dozens of these a week.

Then there is the urgent transfer. An email to the contact themselves, from someone who appears to be their own bank, or their own boss, asking them to confirm payment details or approve something quickly. The phone number in the record gives the attacker a backup channel: a follow-up call from "the bank's security team" referencing the real breach, the real company name, the contact's real name. Every detail checks out, because every detail is true.

Worst of all is the timing. The bank will most likely notify affected contacts directly, which makes "a message from Welcome Savings Bank about the leak" expected mail this week. That is the perfect cover for a phishing email carrying a verification link: the real notice creates the demand, and the fake one arrives first.

None of these need the victim to be careless. They only need the victim to believe their own data, which is exactly what leaked.

The week South Korea's side doors kept opening#

This is the sixth confirmed financial-sector leak in South Korea in four days, and the second at a savings bank. The running list: Shinhan with roughly 25,000 customers on 1 October, then KB Kookmin with 119, Hana Bank with 89, BNK Busan with 11 outsourced workers, and Yegarim Savings Bank with roughly 40,000, all disclosed on 2 October. Welcome Savings Bank lands on the 4th.

I will not connect them. The investigation is underway and no shared attacker or method has been named. What the timing does confirm is that this is not one unlucky bank. The systems around the banking core, the sales tools, the support desks, the corporate client records, are getting hit in sequence, and the savings banks are not exempt. Two of the six are savings banks now.

What we still do not know#

Plenty, and I would rather list it than let it sit between the lines.

The exact scale. "As many as 2,200 records identified so far" is a floor with the ceiling open. Corporate client records may surface in batches as the bank works through its systems.

The method. The bank says it is investigating how the hacking occurred, and no technique, no entry point, no tooling has been named. Anyone describing the attack chain today is guessing.

The original wording. The English report is AI-translated, and the bank's own notice was not read in the original this run. "Corporate names, the names of company contacts, email addresses and phone numbers" is my best rendering of what leaked, and the Korean original may carry distinctions the translation flattened.

Whether any of the data has been used. No misuse has been reported. That sentence has a short shelf life, and the dataset is built for slow, targeted work rather than a mass spam run, which means misuse may never be loud enough to make the news.

A fraud-prevention week, not a password week#

If you are a corporate contact at Welcome Savings Bank, or anyone whose company banks there, treat this as a fraud-prevention week, not a password week. No passwords leaked.

  1. Warn your finance and accounts-payable people. The invoice switch is the move this data enables, so the people who approve transfers need to hear it first. Any change of payment details gets confirmed through a channel you opened yourself: call the number you already have, not the one in the email.
  2. Treat "from Welcome Savings Bank" mail as untrusted until verified. The bank's real notice is coming, which makes this the easiest week of the year to fake one. Open the bank's site yourself or call them. Never click through from the message that raised the alarm.
  3. Expect the phone call version. A caller who knows your company, your name, and your direct number is not proof of anything. Banks do not ask for passwords, one-time codes, or remote access over the phone. Hang up and call back on a number you trust.
  4. Everyone else: check Have I Been Pwned. Turn on its breach notifications, since this breach will not be listed yet. When the next one lands, you want the database telling you before the attacker does. The longer checklist for breach victims is in our breach response guide.

The address that gives the fraud away#

That is the lens I read this breach through: I run AliasFleet, an email-alias service built around one simple idea, that a leaked address should tell you where it came from the moment fraud shows up on it. Here is the honest version of the pitch. No alias would have stopped this breach. A bank's corporate client records are the bank's data, and nothing a customer does at signup prevents a bank from losing them. The claim is narrower than that, and it is the one that matters for what comes next.

The fraud built on this data arrives as email, and if the address you gave Welcome Savings Bank was a dedicated alias, the arithmetic of impersonation changes. A "bank security team" message arriving at the alias you only gave the bank is consistent, still untrusted, still verify. The same message arriving at an address the bank never had is fraud by contradiction: whoever sent it could not have gotten the address from the bank's records. You do not need to judge the logo or inspect the headers. The recipient line names the relationship the address belonged to, and this one does not add up.

That is the mechanism. One alias per relationship turns your inbox into a place where impersonation has to work harder, because every message carries its own origin check. Our leak-tracing guide walks through it, and what an email alias is covers the basics.

That is what AliasFleet exists to do: one address per relationship, pausable in one click, so a leaked address dies alone. The docs explain the mechanics and the free tier covers 10 aliases.

The part the alias does not cover: a work email you cannot change, because your employer owns it. If your corporate address is in the bank's records, no product swaps it out. What still works is the verification habit in the list above, and pausing the alias you used for any bank correspondence where the fraud lands. The email arrives, the address is wrong, and the fraud announces itself. That is a small thing. It is also the only thing in this whole story that you control.

Frequently asked questions

If you are one of the affected corporate contacts, the bank should notify you, but the full scope is still being checked, so treat the count as preliminary. It is not listed on Have I Been Pwned, and corporate contact lists surface there inconsistently; no contact list has surfaced in the reporting read this run. Assume caution, not membership, until the bank confirms.

It is fraud that impersonates someone you already do business with, usually to redirect a payment or extract information. Stolen contact records make it convincing: the attacker knows the company name, the right person's name, and the direct email and phone number. The tell is the ask, not the details.

Not against the breach itself: nothing a customer does stops a bank's system from leaking, and a corporate contact list is the bank's data, not yours. Where aliases help is the second wave. Fraud mail or a phishing email that supposedly came from Welcome Savings Bank but arrived at the wrong address exposes itself on arrival.

It is the sixth confirmed case in the cluster, and the second at a savings bank after Yegarim, but no shared attacker or method has been confirmed. The investigation is ongoing. Timing is confirmed; connection is not.

Never expose your real email address again

Generate private forwarding addresses for newsletters, shops, and apps. Reply through aliases and disable any address with one click if it ever leaks.

Two-way alias repliesCustom domain routingEmail tracker blocking
Get Started FreeView plansFree tier available · No credit card required
Ahsan Luqman

Founder of AliasFleet. Building tools to protect personal inboxes from spam and data breaches.

More articles

All articles