DisclosureLens
GLOBALMalwareTechnologyInformationRansomwareCactusRansom DemandedActor NamedMedium

KYB Corporation

bd_ee3b68baf33a26bd · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Mar 17, 2025

To disclose

—

Affected

Not disclosed

Linked

4 filings

Confidence

50%
Full breach record for KYB Corporation →2 incidents on file

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Cactus on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Group activity: TechnologyDiscovered: 2025-03-17
Listing address (not linked): https://cactusbloguuodvqjmnzlwetjlpj6aggc6iocwhuupb47laukux7ckid.onion/posts/KYBView merged incident timeline

Source: Ransomware.live

Post text · scraped from the leak site

<p>Automotive Parts<\/p><p>KYB Americas Corporation was established in 1974 and is headquartered in Greenwood, IN, USA. KYB manufactures original equipment shocks and struts for carmakers in the Americas and around the globe.<\/p><p>Website: <a href="https://www.kyb.com/">https://www.kyb.com/<\/a><\/p><p>Revenue : $600.5M<\/p><p>Address: 850 N Graham Rd Ste C, Greenwood, Indiana, 46143, United States<\/p><p>Phone Number: ([REDACTED-PHONE]<\/p><p><mark class="marker-yellow"><strong>Download link #1:<\/strong><\/mark> <a href="https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/KYB/PROOF/">https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/KYB/PROOF/<\/a><\/p><p><mark class="marker-yellow"><strong>Mirror:<\/strong><\/mark> <a href="https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/KYB/PROOF/">https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/KYB/PROOF/<\/a><\/p><p><mark class="marker-yellow"><strong>DATA DESCRIPTIONS:<\/strong><\/mark> Confidential engineering data, drawings, personal identifiable information, customers' and partners' information, financial information, confidential information on corporate business and marketing strategies, manufacturing data, correspondence, HR department data, employees' and executives' files, database exports and backups, etc.<\/p><p><img src="/uploads/1_4b26899fb1.png" alt="1.png"><img src="/uploads/5_78aeb63477.png" alt="5.png"><img src="/uploads/3_5789862998.png" alt="3.png"><img src="/uploads/4_3dedf92b86.png" alt="4.png"><img src="/uploads/2_5f0250781d.png" alt="2.png"><img src="/uploads/6_1c1e371224.png" alt="6.png"><\/p>

Incident timeline — mostly unverified

? — ?

Breach window unknown

Mar 17, 2025

Claim posted

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Claim → filing

—

Compliance clock

Not assessable

This filing is one of 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Filing propagation · 4 filings · 3 states

View merged incident ↗
Leak SiteMar 17 · first · this page
Indiana State AG+35d
New Hampshire State AG+36d
Massachusetts State AG+36d

Pattern: first filing Mar 17, last Apr 22 (MA) — a 36-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source ceiling

  • actor name
  • victim claim
  • ransom/leak status
  • discovery date
  • materiality
  • notification
  • affected count
  • confirmed data types
  • compliance clock

The ✕ fields stay blank until a regulatory filing or victim disclosure lands.

About this groupFirst seen 2023-07-03

cactus

According to ransomware.live, The CACTUS ransomware is said to have emerged around March 2023. The group became known for exploiting vulnerabilities to gain initial access and maintain a presence within the organization's infrastructure. There is little known information about the ransomware group, except that it emerged on the mentioned date and, following encryption, a text file named 'cAcTuS.readme.txt' would be created. Additionally, encrypted files were altered to the '.cts1' extension, and data exfiltration and victim extortion were conducted through the use of the service known as Tox. Source: https://github.com/crocodyli/ThreatActors-TTPs

249 tracked hereFull profile →