Skip to main content

Ransomware victim disclosure

All victims

TPI Bearings

listed as tpi.tw · Claimed by Lockbit5 · listed 2 days ago

1d
Age
since listed · data leaked

Status timeline

  1. ListedSep 14, 2026
  2. Data leakeddate unknown

At a glance

Status
Data leaked
Country
Taiwan
Listed on leak site
Sep 14, 2026

About the victim

AI dossier — public-source company profile

TPI Bearings is a Taiwan-based manufacturer of deep groove ball, needle roller, and other precision bearings founded in 1966. The company serves global markets across automotive, motors, machine tools, motorcycles, and bicycles, positioning itself as a leader in custom bearing solutions and Taiwanese manufacturing.

Industry
Precision Bearings Manufacturing
Address
Taiwan (headquarters contact: 886-2-27417321)
Founded
1966

Attack summary

Severity: low — The leak post contains no substantive claim details, no proof files or screenshots advertised, no data inventory disclosed, and no operational impact stated. Only a victim listing with generic text appears present.

The lockbit5 group claims to have attacked TPI Bearings. The leak post provided contains only generic boilerplate text about business management with no specific details about the scope of the attack, data exfiltrated, encryption deployment, or operational impact.

low

What the group claims

Managing a company is a constant process of managing change, solving problems and facing up to chall...

Sources

Source

Indexed 2 days ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About lockbit5

Based on the provided data, LockBit5 appears to be a recently emerged ransomware operation first observed in December 2025, representing what may be a new iteration or rebrand within the LockBit ransomware ecosystem, with primary financial motivations evidenced by their targeting of high-value sectors. Given the LockBit naming convention and the timing of emergence, this group likely operates from Eastern Europe or Russia and may represent either a continuation of previous LockBit operations or a new affiliate group leveraging the established LockBit brand, though specific organizational details remain undocumented by major security agencies. While detailed attack methodologies have not been publicly documented by CISA, FBI, or major security researchers, the group's targeting pattern across 157 victims suggests a broad-spectrum approach focusing on technology, manufacturing, healthcare, and transportation sectors primarily in the United States, Brazil, Germany, Italy, and Mexico. Due to the group's recent emergence in December 2025, there are no publicly documented notable campaigns or major incidents reported by established threat intelligence sources, though the victim count indicates active operations. The group appears to be currently active based on the recent first observation date, though comprehensive analysis from major security agencies has not yet been published given the short timeframe since emergence. The group has been linked to 362 public disclosures across our corpus. First observed on a leak site on December 7, 2025; most recent post September 14, 2026. The operation is currently active.

Timeline of this disclosure

  • September 14, 2026tpi.tw listed by lockbit5 on the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Technology sector, which has 3,577 disclosures indexed across all operators we track. Geographically, tpi.tw is reported in Taiwan, a country with 58 ransomware disclosures in our corpus.

If your organisation is affected

A listing by lockbit5 means tpi.tw appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Monitor for the data appearing on lockbit5's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.