KTU Shipyard
bd_80dc9e38ce2949be · schema v1 · pii pii-v2
Full breach record for KTU Shipyard →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Whitearmor 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
Company: PT Karya Teknik Utama (KTU Shipyard) Location: Batam, Indonesia Founded: 1982 Industry: Shipbuilding & Marine Engineering Website: https://ktushipyard.com/ What the company does KTU Shipyard is an Indonesian shipbuilding company specializing in the construction, repair and maintenance of commercial vessels. Its main products and services include: - Tugboats - Barges - Tankers and cargo vessels - Crane barges - Ship repair and maintenance Company size - Privately owned company. - Approximately 501–1,000 employees. - Multiple shipyard facilities in Indonesia. - Claims to have built approximately 2,200 vessels. Annual Revenue ~USD 200 million Key Business Information - Business model: B2B shipbuilding and marine services. - Customers: Shipping companies, marine logistics operators and offshore businesses. - Main market: Indonesia and regional maritime markets. - Competitive advantage: Established shipbuilding experience, multiple facilities and diverse vessel manufacturing capabilities. What was accessed: Internal ticketing systems, All users drive (including business, customer, confidential files over 3tb of data), customer data, etc. You have 20 days to reach out or let it be your downfall. Attatched: Is a sample file from recent user drives, and a screenshot showing POA (proof of access) We can be very reasonable and this can go well or it can not. You can start contact at the email: [REDACTED-EMAIL] https://gofile.io/d/G981x5Rl https://gofile.io/d/99sTtibR (backup sample files)
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 30, 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.