YAZAKI Corp was listed on 07 December 2025 by the incransom ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). incransom listed 34 organizations that month and 1043 in total.
- Listed 347 days ago.
- 896 organizations were listed by all groups in December 2025, see the month.
- 179 in Manufacturing that month.
- 9 in JP that month.
- 1 other listing for the same organization.
Updated 2026-11-19 05:55 UTC. Data: public leak-site listings. How we work.
Named in 2 separate listings
Another listing name this organization: a different group, or the same group months apart. Each is a claim the group published, not a confirmed breach. The same group listing it again within a few months is not counted: that is the same listing sent twice or moved from countdown to published.
Threat Group Post & Evidence
- Listed by
- INC Ransom 1,043 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.
The Yazaki Group is a global company best known for being a leading supplier of automotive wire harnesses, but it also produces other products like environmental systems and instrumentation equipment. The company's focus is on providing quality products and services to its customers, with a global presence that allows for responsive, just-in-time delivery. However, the company has also faced legal issues, including a significant fine for its role in an automotive parts price-fixing scheme. The data size is at 350 GB. WE HAS COLLECTED SUCH DATA AS: - Confidential documents - Clients Data - NDA - Financial data - Operations - Corporate data - HR data (including employee medical records) - Business Agreements - Development - Drawings - Technological production requirements and all documentation for the production of parts for BMW, NISSAN, SCANIA and many other global brands And a lot of oth…
Show the full post (959 characters)
The Yazaki Group is a global company best known for being a leading supplier of automotive wire harnesses, but it also produces other products like environmental systems and instrumentation equipment. The company's focus is on providing quality products and services to its customers, with a global presence that allows for responsive, just-in-time delivery. However, the company has also faced legal issues, including a significant fine for its role in an automotive parts price-fixing scheme. The data size is at 350 GB. WE HAS COLLECTED SUCH DATA AS: - Confidential documents - Clients Data - NDA - Financial data - Operations - Corporate data - HR data (including employee medical records) - Business Agreements - Development - Drawings - Technological production requirements and all documentation for the production of parts for BMW, NISSAN, SCANIA and many other global brands And a lot of other VERY IMPORTANT information!
Amounts as written
- 350 GB
Kinds of data mentioned
-
Medical or patient records
“…Financial data - Operations - Corporate data - HR data (including employee medical records) - Business Agreements - Development - Drawings - Technological production requirements…”
-
Customer or client data
“…is at 350 GB. WE HAS COLLECTED SUCH DATA AS: - Confidential documents - Clients Data - NDA - Financial data - Operations - Corporate data - HR data (including employee medical…”
-
Employee and HR records
“…NDA - Financial data - Operations - Corporate data - HR data (including employee medical records) - Business Agreements - Development - Drawings - Technological production…”
-
Contracts and legal files
“…HAS COLLECTED SUCH DATA AS: - Confidential documents - Clients Data - NDA - Financial data - Operations - Corporate data - HR data (including employee medical records)…”
Plain-English summary AI-written
The group says it has collected 350 GB of data, including confidential documents, client data, NDAs, financial, operational and corporate information, and HR data that includes employee medical records.
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 YAZAKI (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 YAZAKI 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 YAZAKI 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, employee and hr records.
- If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.
Within 30 days
- Keep watching YAZAKI 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 YAZAKI
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.
Within 3 days
- Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 350 GB. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties Japan: the APPI requires reporting certain leaks to the Personal Information Protection Commission and notifying affected people. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Japan.
Within 30 days
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
- Check shared suppliers and software List the suppliers and software you share with other Manufacturing organizations and ask them whether they were affected. Why: incransom listed 19 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)
88/100 • CRITICALA 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.