Home All Victims ford.mx

ford.mx

krybit

This record tracks a ransomware attack claimed by the krybit group against ford.mx. It collects the publicly disclosed attack details — sector, location and timeline — as published on the operator's leak site and indexed by Breach House.

Window Zero

EXPOSURE GAP

Window Zero is the time the breach stayed in the open before anyone said so — the gap between when the attack was first discovered on the operator's leak site (t1) and when it was publicly disclosed (t2). The wider this window, the longer victims, staff and customers were exposed with no warning.

68days open
t1 · Published t2 · Pending
Jun 28, 2026Not disclosed yet
Country
Business Category
Manufacturing / Engineering
Employees
+1000
Discovered
2026-06-28
Published
June 28, 2026
Leak Status
pending
checked 2026-09-02
Disclosed / Notified
Not disclosed yet
Victim ID
f3kRxyPR4D25

Attack Summary

Ford Motor Company, S.A. de C.V. (Ford de Mexico) is the Mexican subsidiary of Ford Motor Company (USA), the first autom...

Leak Screenshots

1 CAPTURED

Captured directly from the operator's leak site by our collector, last checked 2026-09-02. Verdict evidence: [H7] 00m 00s

Capture history — 2 day(s) tracked. Content is locked.

2026-09-04
2026-09-02
Showing the latest capture only
Unlock the 2 captures already taken.

Dark Web Exposure

Findings for ford.mx — indexed by HaveIBeenRansom.
271
found in Infostealer logs
14
found in Traditional breaches
5
found in Ransomware leaks
Apollo.io DB 816millions.rar
Database World ROC · breach
••• emails
udemy.com.zip
Database World ROC · breach
••• emails
EnCom Polymers
losttrust · ransomware
••• emails
pureincubation-com.7z.001
Database World ROC · breach
••• emails
Leak volumes are locked
Sign in to reveal how many records each source exposed.
Want the complete picture — passwords, machines, full leak files? It's all searchable on HaveIBeenRansom.
Search this victim →
Visit Website Original Post View Group: krybit
Legal Disclaimer: This ransomware victim record reflects information published on the operator's leak site. Breach.house only records what the operators themselves publish in the open. We take screenshots of their public pages and keep the proof material they post there, so that a listing can be verified and its status tracked over time. We do not purchase data, we do not solicit or encourage its publication, we do not access any private system, and we do not alter anything we record. Nothing is offered for download here, and detailed content is not published on this page or anywhere else on the public site: access to it is restricted to vetted customers under contract, for incident response, due diligence and cyber-resilience work. Breach.house is not affiliated with, and does not act on behalf of, the operators who publish this material. If you represent an organisation or individual named here and want a record reviewed or removed, contact us and we will act on it.