Fukoku Co. Ltd. was listed on 09 January 2025 by the spacebears ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). spacebears listed 11 organizations that month and 159 in total.
- Listed 679 days ago.
- 613 organizations were listed by all groups in January 2025, see the month.
- 102 in Manufacturing that month.
- 6 in JP that month.
Updated 2026-11-19 06:19 UTC. Data: public leak-site listings. How we work.
Threat Group Post & Evidence
- Listed by
- Spacebears 159 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
In 2022, Fukoku Co., Ltd. celebrates its 90th anniversary.Since our founder, Shinkichi Koga, began manufacturing and selling futons in Yanagawa City, Fukuoka Prefecture, Fukoku has consistently been of service to our customers through "textiles."Today, we enjoy patronage from a wide range of industries, from futons (bedding) to the automotive, housing, and nursing care fields, but all of this is a business that derives from the "textile = thread" that we have known since our founding.In 2009, we created a new brand logo,which is "CCC Chasic."• Date bases. accounting. sales. purchasing. drawings. prototypes. production cycles. https://fukoku-jp.com/
Kinds of data mentioned
-
Accounting and ledgers
“…2009, we created a new brand logo,which is "CCC Chasic."• Date bases. accounting. sales. purchasing. drawings. prototypes. production cycles. https://fukoku-jp.com/”
-
Customer or client data
“…City, Fukuoka Prefecture, Fukoku has consistently been of service to our customers through "textiles."Today, we enjoy patronage from a wide range of industries, from futons…”
Plain-English summary AI-written
The group says it holds databases, accounting and sales records, purchasing information, drawings, prototypes, and production-cycle data.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Fukoku (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Fukoku directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Fukoku can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data.
- Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: accounting and ledgers.
Within 30 days
- Keep watching Fukoku A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Fukoku
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: customer or client data.
- Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: accounting and ledgers.
Within 3 days
- Check regulatory and stakeholder notification duties Japan: the APPI requires reporting certain leaks to the Personal Information Protection Commission and notifying affected people. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Japan.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Manufacturing organizations and ask them whether they were affected. Why: spacebears listed 2 other Manufacturing organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
60/100 • ELEVATEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.