Oztugotomotiv
bd_35d9d6355052168d · schema v1 · pii pii-v1
Full breach record for Oztugotomotiv →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom 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.
Source: Ransomware.live
Post text · scraped from the leak site
Öztuğ Otomotiv & Endüstri is a Turkish company established in 1990 in Bursa, specializing in the production of high-precision components for the automotive, industrial, defense, and aerospace sectors. The company offers comprehensive services including design, mold manufacturing, and serial production of plastic, metal, and rubber parts, as well as industrial seals and vibration dampers. Öztuğ Otomotiv utilizes modern equipment (high-tonnage presses, progressive dies) and adheres to international quality standards, including a zero-defect principle and compliance with OEM standards. Financial performance (not publicly disclosed, but the company positions itself as a stable business): As of 2025, the company reports over 35 years of successful operations, more than 300 employees, and three production facilities with a total enclosed area of 12,000 m2. Structure and facilities: The company operates three production sites in Hasantığla, Nilüfer (Bursa), and Adapazarı. As of 2025, the workforce comprises over 300 specialists. Production capabilities include plastic injection, metal forming, and rubber molding lines. Laek: 100GB WE HAS COLLECTED SUCH DATA AS: - Confidential documents - Clients Data - NDA - Financial data - Operations - Corporate data - Business Agreements - Development - Financial databases, all transactions, all clients And a lot of other VERY IMPORTANT information!
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 3, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
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.