Imagine opening your banking or brokerage app and wondering, quietly, whether your details are still just yours?
Not because you clicked a dodgy link. Not because you lost your phone. Just because the company holding your money was hit, and you found out about it in the news.
That is the position thousands of people in South Korea were put in this week, as a hacking wave that had already touched banks and savings banks spread to brokerages, an asset manager, and a crypto exchange.
This is not a story about one company making one mistake. It is a story about a wave — and waves are scarier than single incidents, because you never quite know where the next one lands.
Contents
- What happened, in order
- What exactly leaked from Daishin
- Bithumb and Mirae Asset: what we know, and what we do not
- This did not start this week
- Why financial firms are such tempting targets
- The AI angle, and why it keeps coming up
- What to do if you are a customer
- What to do if you are not a customer
- What happens next
- Frequently asked questions
- The bottom line
What happened, in order
Let us lay out the facts first, because this story has a lot of moving parts and it is easy to lose track of who was hit and when.
On 28 October 2026, reports described a fresh round of data-leak disclosures in South Korea. Daishin Securities said personal and credit information belonging to 38,490 customers had been leaked. Mirae Asset Asset Management was also reported to have suffered a hacking incident, with authorities assessing the situation. And cryptocurrency exchange Bithumb acknowledged a breach of its internal mobile system that exposed personal information.
Daishin’s timeline is the most detailed of the three, and it is worth walking through slowly.
The company said it first detected signs of unauthorized access on 17 October, to a server supporting remote securities-account opening for discretionary investment services. In plain English: a server involved in opening investment accounts from a distance, without visiting a branch in person.
Daishin said it blocked the internet addresses used in the attack, including addresses used to bypass access restrictions, and notified regulators. Working with the Financial Security Institute, the brokerage reviewed about 60,000 requests disguised as legitimate service traffic over a 10-day investigation. It confirmed the information leak on 26 October.
Stop for a second on that number: 60,000 requests, disguised as normal traffic, reviewed over ten days. That is not someone rattling a doorknob once. That is someone trying very hard to look normal while doing something that is not normal at all.
And that is one of the hardest problems in security. A system that blocks every unusual request will also block real customers. A system that lets everything through will let attackers through too. The middle ground — spotting the fake traffic hiding inside the real traffic — is where these investigations live.
What exactly leaked from Daishin
This is the part most people skip to, and rightly so. If you are a customer, you do not care about the technical diagram. You care about what of yours is now out there.
According to Daishin’s disclosure, eight categories of information were exposed:
Names, email addresses, postal addresses, communications IDs, bank names, bank account numbers, Daishin securities account numbers, and mobile phone numbers.
Read that list again, slowly, because it is worse than a single leaked password.
A password can be changed. An email address can, with effort, be changed. But your name, your postal address, your bank name, and your account numbers are not things you casually rotate. They are the details that make a phishing message look convincing. A scammer who knows your name, your bank, and your securities account number does not need to guess. They can write a message that sounds like it already knows you.
That is why data leaks like this have a long tail. The leak itself is one event. The phishing attempts, the impersonation calls, and the “we need to verify your account” messages can go on for months afterwards. If you are affected, the most important thing is not just what happened on 26 October. It is what you do about suspicious messages in November, December, and beyond.
It is also worth being honest about what we do not know from the reports so far. The disclosures describe personal and credit information being leaked, and list the eight categories above. They do not, in the reporting we have, say that funds were stolen from customer accounts, and we should not invent that claim. A data leak and a theft of money are different things, even when they are both serious. Treat the leak as confirmed. Treat anything beyond it as unconfirmed until the company or regulators say otherwise.
Bithumb and Mirae Asset: what we know, and what we do not
Bithumb’s disclosure was shorter, but no less worrying for its users.
The crypto exchange said its internal mobile system was hacked, resulting in a leak of personal information. The phrase “internal mobile system” matters, because it suggests the breach was not simply someone guessing a customer’s password. It was a system inside the company, used for mobile services, that was compromised.
Beyond that, the public reporting so far does not give a customer count for Bithumb, or a detailed list of exactly which fields were exposed, in the same way Daishin’s disclosure does. That does not mean the leak was small. It means the details are not yet public, or not yet confirmed. If you use Bithumb, the safe move is to assume your personal information could be involved until the company tells you otherwise, and to take the protective steps at the end of this article anyway.
Mirae Asset Asset Management sits in a similar position. It was reported to have suffered a hacking incident, with authorities assessing the situation. That is a real report, but it is not yet a detailed disclosure. We do not have, from the reporting so far, a confirmed list of what was taken, or how many people were affected. Again, do not fill in the gaps with guesses. Watch for an official update from the company or from regulators, and act on the precautions in the meantime.
This restraint matters, because in a fast-moving hacking wave, rumours travel faster than confirmations. A careful article that says “we do not know yet” is less exciting than a confident article that invents a number. It is also a lot more useful.
This did not start this week
Here is the context that turns three incidents into a wave.
South Korea’s Financial Services Commission said on 14 October that cyber incidents had been identified at 16 firms, with roughly 100,000 records exposed. That was an interim tally, before the latest disclosures, and investigators were still examining whether the attacks were connected.
Think about that for a moment. Sixteen firms. Roughly 100,000 records. And that was before Daishin, Mirae Asset, and Bithumb were added to the list.
Data-leak reports had, by 28 October, become more or less a daily affair in South Korea that month, with a brokerage, an asset manager, and a crypto exchange becoming the latest to join a growing list of financial businesses hit by cyberattacks. The cases added to a wave of breaches across banks, savings banks, and other financial businesses.
That pattern — banks first, then brokerages and crypto — is what makes security experts nervous. It suggests attackers are working through a sector, learning as they go, rather than hitting one random target and disappearing. It also raises a question investigators are still examining: are these attacks connected, or are they separate groups taking advantage of the same weak moment?
We do not have a confirmed answer to that yet, and we should not pretend we do. The honest answer is that investigators are looking at it, and the rest of us should act as if the wave could continue, not as if it is definitely over.
If you want the wider picture of how attacks are changing this week, it helps to read this alongside our other security coverage. The same week brought critical PHP flaws being scanned across the internet, which we cover in Critical PHP Flaws Are Being Scanned Right Now — WordPress Owners, Patch This Week. Different technology, same underlying shift: attackers are automating the search for weak points, and they are not limiting themselves to one kind of target.
Why financial firms are such tempting targets
It is easy to ask, “Why do these companies keep getting hacked? Do they not have security teams?”
They do. Financial firms usually have larger security teams than most companies. But they are also more tempting targets, for a few simple reasons.
First, they hold exactly what attackers want: identity details, account numbers, and access to money. A hacked recipe blog is annoying. A hacked brokerage is valuable.
Second, they have a huge attack surface. That is a technical phrase for a simple idea: lots of doors. Branches, apps, websites, remote account opening, customer service systems, partner systems, mobile systems. Every door is useful for customers. Every door is also something that needs to be defended.
Daishin’s case is a good example. The server involved supported remote securities-account opening. That is a genuinely useful service — open an investment account without travelling to a branch. But it is also a service that, by design, accepts requests from the internet, from people the company has never met in person. Designing that safely is hard. Spotting fake requests hidden among 60,000 real-looking ones is harder.
Third, financial firms are interconnected. A customer uses a bank, a brokerage, and a crypto exchange. An attacker who learns your details from one leak can try them, in a convincing phishing message, against another. That is why a leak at one firm can put you at risk at firms that were never hacked at all.
None of this excuses a leak. It just explains why “just be more secure” is not a complete answer. Security is not a single lock. It is a whole building, with many doors, and attackers only need to find one that was left ajar.
The AI angle, and why it keeps coming up
You may have noticed that AI keeps appearing in this week’s security stories, and South Korea is no exception to the wider trend.
Across the industry, AI tools are making it easier to find weaknesses, generate convincing phishing messages, and run scans at a scale that would have been exhausting for a human team. We explore that shift in AI Is Now Finding the Weak Spots in Everyday Websites, where everyday services — libraries, train bookings, university systems — are now in the firing line, not just big banks.
That does not mean every attack in South Korea was AI-powered. The reports so far do not make that specific claim about Daishin, Mirae Asset, or Bithumb, and we should not add it. What we can say is that the wider environment has changed. Automated scanning, disguised traffic, and large-scale probing are now normal parts of the threat landscape, and financial firms are operating inside that landscape every day.
It is also worth keeping the other side of AI in mind, because otherwise every AI story starts to sound like a horror story. The same technology that can scan a website can also help a person in a much smaller, kinder way. We recently wrote about a man who lost a white earbud in white gravel, and how ChatGPT found it in under five minutes from closer photos he uploaded. That story travelled because it was human, useful, and honest about its limits.
AI, in other words, is not a villain or a hero. It is a multiplier. It multiplies the patience of a person searching for an earbud, and it multiplies the speed of a scanner searching for a weak server. The defence does not change much either way: keep your details guarded, keep your accounts locked down, and do not trust a message just because it sounds like it knows you.
What to do if you are a customer
If you use Daishin, Mirae Asset, Bithumb, or any South Korean financial service, here is a calm, practical checklist. None of this requires technical skill, and none of it involves panic.
1. Change your passwords, starting with email.
Your email is the key to almost everything else, because password resets go there. Change your email password first, using a strong, unique password. Then change your brokerage, asset management, and exchange passwords. Do not reuse the same password across them. A password manager, if you use one, makes this much less painful than it sounds.
2. Turn on every second factor you are offered.
App-based codes and security keys are stronger than text-message codes, but any second factor is better than none. Turn it on for your financial accounts and for your email. If a service offers login alerts, turn those on too, and actually read them.
3. Expect phishing, and plan for it.
Assume that someone may now know your name, your bank, and possibly your account numbers. That means a message that says “Dear [your name], we noticed unusual activity on your [bank name] account” is no longer proof that the sender is legitimate. It could be proof that they read a leak.
The rule is simple and boring, and it works: never click a link in a message about your money. Open the app yourself, or type the official website address yourself, and check there. If a caller claims to be from your bank or brokerage and asks for a code, a password, or a transfer, hang up and call the official number yourself.
4. Watch your accounts, closely, for the next few months.
Check your transaction history more often than usual. Set up transaction alerts if your bank or brokerage offers them. Look for small, unfamiliar transactions as well as large ones, because attackers sometimes test with a small amount first. If you see anything you do not recognise, report it through the official app or number immediately, not through a reply to a suspicious message.
5. Be extra careful with account-opening offers.
Because Daishin’s incident involved remote account opening, be wary of any message offering to “help” you open, verify, or recover an account, especially if it arrives out of the blue. Real account opening happens through official channels, at a pace you control. Urgency — “verify in the next hour or your account will close” — is a classic pressure trick. Real companies can wait while you check through official channels.
6. Do not share more details to “prove” you are a victim.
If someone contacts you claiming they can check whether your data was leaked, and asks you to send them your account number, ID number, or password to confirm, stop. That is exactly the kind of detail a leak makes valuable. Check your status through the company’s official notice, or through your regulator’s announcements, not through a stranger offering to help.
What to do if you are not a customer
You might be reading this from the United States, Bangladesh, or anywhere else, thinking: “I do not use these companies, so this does not affect me.”
It still affects you, in a quieter way.
First, the same tactics travel. Disguised traffic, remote account opening abuse, and phishing built from leaked details are not Korean inventions. They are global tactics, and they will show up in your country, against your banks, sooner or later.
Second, the lesson about data is universal. The eight categories leaked from Daishin — name, email, postal address, communications ID, bank name, bank account number, securities account number, mobile number — are the same categories most financial firms hold about you, wherever you live. A leak anywhere is a reminder to tighten your own accounts everywhere.
Third, if you run a website or a small business, this week is a reminder to patch your own systems too. Our checklist for site owners is in Critical PHP Flaws Are Being Scanned Right Now — WordPress Owners, Patch This Week, and the core advice is the same: update, back up, delete what you do not use, and check who has access.
Security news can feel distant when it happens in another country. The habits it teaches are not distant at all.
What happens next
The honest answer is: we do not know yet, and anyone who tells you they do is guessing.
Regulators are assessing the Mirae Asset incident. Bithumb’s users are waiting for more detail about what was exposed in its internal mobile system. Daishin’s customers are waiting to see whether the 38,490 figure is final, or whether further review changes it. Investigators are examining whether the attacks across 16 firms, and now more, are connected.
What we can reasonably expect is more disclosures, not fewer, in the short term. That is how waves work. Companies investigate, confirm, and then announce, often days or weeks after the first detection. Daishin detected signs on 17 October and confirmed the leak on 26 October. That nine-day gap is not a delay for the sake of it. It is the time it takes to review tens of thousands of requests and work out what actually left the building.
In the meantime, the best approach for readers is steady, not frantic. Change passwords. Turn on second factors. Do not click money links in messages. Check your accounts. Wait for official updates, and treat unofficial numbers with caution.
Big companies are also moving fast in other directions this week, which is part of the wider context. Microsoft, for example, is reshaping its workforce while investing heavily in AI, as we covered in Microsoft Offered Buyouts to 60,000 Staff While Pouring Money Into AI. That is a different story, in a different country, but it is part of the same week in tech: huge AI spending, big workforce changes, and security incidents landing in the middle of it all. It is a lot to keep track of, which is exactly why simple, repeatable habits matter more than trying to follow every headline.
Frequently asked questions
Were funds stolen from Daishin or Bithumb customers?
The reports so far describe personal information being leaked, and in Daishin’s case, list the eight categories exposed. They do not confirm that funds were stolen from customer accounts. Do not assume a theft happened, and do not assume it did not — wait for an official update, and check your own account history in the meantime.
How many Bithumb customers were affected?
That number has not been confirmed in the reporting so far. Bithumb acknowledged a breach of its internal mobile system that exposed personal information, but a customer count and a detailed field list have not been published in the same way as Daishin’s disclosure. Treat your details as potentially involved until the company says otherwise.
What about Mirae Asset?
Mirae Asset Asset Management was reported to have suffered a hacking incident, with authorities assessing the situation. Detailed confirmation of what was taken, and how many people were affected, has not yet been published in the reporting we have. Watch for an official update.
Are these attacks connected?
Investigators are examining whether the attacks are connected. That examination was already under way when the Financial Services Commission reported incidents at 16 firms on 14 October, and it continues with the latest disclosures. There is no confirmed public conclusion yet.
I am not in South Korea. Should I still change my passwords?
If you reuse passwords across services, yes, and not just because of this wave. A leak anywhere can be used to try logins everywhere, especially when people reuse the same password. Unique passwords for financial accounts and email are one of the highest-value habits you can build.
How do I spot a phishing message built from leaked data?
It will look more convincing than a generic scam, because it may use your real name, your real bank, or your real account type. The giveaway is usually the action it wants: click a link, download a file, share a code, or transfer money urgently. Real financial firms will not ask you to do those things through a message link. Always go through the official app or website yourself.
The bottom line
Thirty-eight thousand, four hundred and ninety customers at one brokerage. An asset manager under assessment. A crypto exchange’s internal mobile system breached. Sixteen firms and roughly 100,000 records before this latest round was even counted.
Those numbers are serious, but they are not the whole story. The whole story is what happens next, in inboxes and on phones, when leaked details are used to write messages that sound like they already know you.
So change your passwords. Turn on that second factor. Do not click money links in messages. Check your accounts, and keep checking them for a few months, not just this week.
A leak is an event. Good habits are what stop an event from becoming a second, more personal loss.