Stolen Data Reached a Leak Site — The Ransomware Attack on Bell Holdings, and How to Prepare After Information Has Appeared in Public

Hello, I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. I am a former funeral director, and I now live in an old house in Kurashiki, Okayama, working together with my AI butler, Moka.
This time, the story carries a slightly different weight from the incident articles I have written so far. It was confirmed in the company’s announcement that stolen information had not only possibly gone out — it had actually appeared on the attacking side’s site (a leak site).
The result first
Here is the conclusion, up front.
- The internal system of Bell Data Co., Ltd., a group company of Bell Holdings Co., Ltd., was hit by a ransomware attack in the early hours of September 19, 2024. Ransomware is a mechanism that encrypts information so it cannot be used, and threatens to restore it in exchange for money
- As a result of an investigation by an outside specialist company, it was found that information stored in the internal system may have been viewed, at the very least, by an outside third party. The total was 47,359 cases, including business-card information of business partners’ personnel and employee information
- Furthermore, it was confirmed that some of the information had been uploaded to a leak site — a site where the attacking side publishes stolen information
- The company says that, at present, it has received no report that secondary damage, such as misuse of personal information, has occurred
- The entry point is believed to have been unauthorized access via VPN equipment, the announcement says. A VPN is a tool that provides a secure route into a company’s system from outside. That tool itself became the entry point
What happened — what the announcements confirmed
First, the first announcement by Bell Data Co., Ltd. (September 26, 2024).
- In the early hours of Thursday, September 19, 2024, the company’s internal system was hit by a ransomware attack
- Because infection was confirmed in part of the internal system, all servers suspected of infection were temporarily isolated from the network
- As a result, business was disrupted, including delays in some normal operations (such as order placement and receiving operations)
- A response team was set up, and measures were carried out, including confirming the situation, preventing the spread of infection, restoring the system, and preparing for a possible second attack
- Regarding whether there had been an information exposure, the company reported the matter to the police and was proceeding with confirmation in cooperation with an outside specialist company
The subsequent course of events has been conveyed in reporting. In the third report on October 9, 2024, it was announced that the outflow of some information concerning business partners had been confirmed (according to reporting by ScanNetSecurity).
Then, on March 17, 2025, Bell Holdings Co., Ltd. issued a “Notice and Apology Regarding the Ransomware Attack on Our Company” and published the results of the investigation. The main contents are as follows.
- As a result of an investigation by an outside specialist company, it was found that information stored in the company’s internal system may have been viewed, at the very least, by an outside third party
- Reports had been made to the Personal Information Protection Commission and to the Japan Users Association of Information Systems (JUAS), and a damage report had also been filed with the police
- The internal system had already been restored, and at present there was no impact on business
- As a contact point for inquiries, a dedicated personal information desk (the Security Incident Response Office) was set up at Bell Data Co., Ltd.
The information affected — what the 47,359 cases contain
The personal information that may have been viewed, as shown in the announcement of March 17, 2025, is as follows.
- Number of cases affected: 47,359 (including 444 cases of information on the company’s employees)
- Business-card information concerning personnel of business partner companies and others (name, company and department, job title, and the telephone number, email address and address of the company they belong to)
- Personal information of the company’s employees (name, department and email address)
What catches the eye here is the business-card information. Business cards are something people exchange as a matter of course in business relationships. The name, company, department, job title, telephone number, email address and address written on those cards had gathered on a scale of more than 40,000 cases. From the side that handed over a card, it is the information of “a single business card,” but from the place where it gathered, it is a list of business partners’ personnel itself.
One more thing: let me write the line in the wording precisely. The announcement’s wording is “may have been viewed.” It has not been established that all 47,359 cases were taken outside. What was confirmed to have been taken out is the “some information” written about next.
Not a “possibility” — confirmed to have appeared in public
The announcement of March 17, 2025 says this:
It has been confirmed that some information has been uploaded to a so-called leak site, but at present we have received no report that secondary damage, such as misuse of personal information in connection with this matter, has occurred.
A leak site is a site prepared by the attacking side to publish stolen information. The attackers threaten, “If you do not pay, we will publish the stolen information,” actually put some of it out in public, and increase the pressure. It is the representative form of ransomware attacks today.
In the incident articles I have written so far, exposure was at the “possibility” stage. This case is one step beyond that. It was confirmed, in the company’s own announcement, that some of the stolen information had actually appeared in public.
About the fear that lies beyond this “appearing in public,” I say this, in my own voice.
The frightening thing about unauthorized access is that stolen information is bought and sold on dark websites and the like. I think it is that, in places you know nothing about, accounts are opened and certificates are created, and another version of yourself comes to exist.
About the calculation of the stealing side, too, I say this.
There is no way the person who stole it would brazenly come out into the open. Even if they sell one person’s information for just a few hundred yen, when it is the information of tens of thousands of people, a large amount of money ends up in their pocket. And once they get a taste for it, they will keep repeating the same thing to keep earning.
About how stolen information sells, too, I say this.
Personal information sells even when it is duplicated.
To close, I say this.
It means that name lists sell — now, just as they always have.
What was affected this time was the business-card information of business partners’ personnel, and employee information. Just like the paper name lists of the past, information in which “who, at which company, in what job title, and where to contact them” is all together becomes, in any era, material for the side that would misuse it. After it has appeared in public, that information could be used for impersonating contacts, or as a foothold for another attack. The announcement’s line that “no report of secondary damage has been received” is a statement as of the present moment; the information that has appeared in public itself does not come back.
The entry point was VPN equipment
Regarding the cause, the announcement of March 17, 2025 writes this:
It is believed that a third party accessed our servers without authorization via VPN equipment.
VPN equipment is a tool that creates a route into a company’s system from outside, for working from home and for connections between sites. It is a tool placed there for safety, but if a weak spot (a vulnerability) remains in that tool, that spot becomes the biggest entry point. Which company’s equipment, and what kind of weak spot it was, has not been made public in the announcement. This article will not jump to conclusions about that either.
The same form of entry point also occurred at a national institution. In the unauthorized access to the Digital Agency’s Government Shared Services (GSS), announced in September 2025, the entry point was also an already known vulnerability in VPN equipment. The details are covered in separate articles.
- The Government’s Shared Platform Was Entered — Unauthorized Access to the Digital Agency’s GSS and the Possible Exposure of About 246,000 Items of Personal Information, and How to Protect VPN Weak Spots
- You Can Find the ‘Weak Spots’ Yourself, Before Someone Breaks In — The Basics of Vulnerability Assessment and How to Protect a Small Site
That checking, which finds weak spots in advance, is called vulnerability assessment. Even when people take care with updates to servers and computers, updates to equipment that connects to the outside tend to be put off. I think this case and the GSS case showed that habit from the side of large organizations.
How to prepare after information has appeared in public — for those who entrusted it
Your name and contact details may have appeared in public through an incident at a business partner or employer. For when you find yourself in that position, here is how to prepare, in a general form.
- Be most suspicious of contacts about “identity verification” or “please register again”: Email addresses and telephone numbers that have appeared in public are more likely to receive plausible-looking contacts. Do not proceed with a procedure based only on guidance by email or telephone; contact the official desk yourself and verify
- Be careful of contacts tied to business-card information: A contact that knows your company name, department and job title can look genuine. “Knowing things about you” and “being genuine” are different matters
- Check for reuse of passwords: Is your work email address being used to log in to other services? If there is reuse, information that has appeared in public can become the key to another entry point
- When you are worried, go to the company’s desk: In this case, a dedicated personal information desk has been made public. The surest way to confirm whether your own information is affected is through the published desk
Lessons for those who hold it — for those who hold employee and business partner information
- Count business-card information, too, as “personal information you are holding”: People may take care with customers’ information, yet business cards gathered through work, and employee information, tend to be placed outside the shelf of protection. A gathered name list becomes, as it is, the scale of material that can be targeted
- Put equipment that connects to the outside on the shelf of checking: Peripheral equipment such as VPN equipment, in particular, should be put into the regular work of updates and checking. Even if you are watching only the servers, the entry point is elsewhere
- Keep issuing reports even while the investigation is under way: In this case, publication continued in stages — the first report (September 26, 2024), subsequent reports, and the investigation results (March 17, 2025). The form of putting out what has been learned, in order, becomes material for the side that entrusted its information to proceed with its own preparations
- Communicate “may have been viewed” and “confirmed to have appeared in public” separately: Writing the scope of possibility and the scope of what has been confirmed separately leads to the right preparations on the reader’s side. This case’s announcement was written in a way that lets that line be read
Where the line is — what is not known
The bigger the stir, the more the line matters. As of this article, I will honestly list what has not been made public.
- The details of the VPN equipment have not been made public: Which equipment, and what kind of vulnerability it was, is not written anywhere in the announcements
- The name of the leak site, and the details of the information posted, have not been made public: The announcement is limited to the scope that the upload of “some information” was confirmed. This article will not write beyond that
- Whether a ransom was paid has not been made public: This article will not touch on it either
- The 47,359 cases are the number that “may have been viewed”: It is not a number established as having all been taken out
- As for secondary damage, as of the announcement, the company had “received no report”: No new announcement after that could be confirmed as of November 21, 2026
- This article is based on announcements and reporting that could be read as of November 21, 2026. If new announcements come out, the contents will change
The fact that stolen information actually appeared in public is a heavy one. Even so, I think the precision of the lines drawn in the announcement, and the way publication continued in stages, are worth recording as the work of the side that holds information. And the side that entrusted its information proceeds, on its own side of life, with preparations for after information has appeared in public. That is what can be taken home from this incident.
Sources
- Bell Data Co., Ltd., “Report on the Ransomware Attack on Our Company and the Response Measures Taken” (当社へのランサムウェア攻撃に関するご報告と対応措置について) (September 26, 2024) https://www.belldata.com/news/topics/240926.html
- Bell Holdings Co., Ltd., “Notice and Apology Regarding the Ransomware Attack on Our Company” (当社へのランサムウェア攻撃に関するお知らせとお詫び) (March 17, 2025) https://www.bell-group.jp/news/post-204.php
- ScanNetSecurity, “Ransomware attack on Bell Data, outflow of some information concerning business partners confirmed” (ベル・データにランサムウェア攻撃、取引先に関する一部情報の流出を確認) (October 24, 2024); and “Upload to a leak site confirmed — the ransomware attack on Bell Data” (リークサイトへのアップロードを確認 ~ ベル・データへのランサムウェア攻撃) (March 27, 2025)
- Cybersecurity.com, “Concern over exposure of 47,000 cases due to ransomware infection; some information posted on a leak site — Bell Holdings” (ランサム感染で4万7千件の漏えい懸念一部情報はリークサイト掲載│ベル・ホールディングス) (March 24, 2025) https://cybersecurity-jp.com/news/109284
- For the meanings of terms, see the Security Laboratory glossary: Security Glossary — Ransomware (S-45), Personal Information (S-09), Exposure (S-46), Vulnerability Assessment (S-53)
Entrance (other languages)