Kenaitze Indian Tribe
bd_a3fdc985825c4297 · schema v1 · pii pii-v1
Full breach record for Kenaitze Indian Tribe →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
Cybersecurity incident limits Kenaitze Indian Tribe services in Alaska. Kenaitze Indian Tribe: The Kenaitze Indian Tribe was the victim of a cybersecurity incident that disrupted its telephone, email, and computer systems for more than a week. The incident, linked to a ransomware attack attributed to the group known as TheGentlemen, has resulted in the limitation of public services. The tribe has not confirmed the ransomware attack, data theft, or ransom demand, but it has used temporary phone lines to maintain essential services. Linked ransomware group: thegentlemen.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 27, 2026
Press report
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitethegentlemenbd_4b9db84c571ca81c2026-07-31 · +4dCandidate
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.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
thegentlemen
According to ransomware.live, The Gentlemen is a RaaS group that emerged in July–August 2025, rapidly claiming over 320 victims across 17+ countries by offering affiliates a 90% revenue share, deploying a Go-based locker against Windows, Linux, NAS, and BSD systems; a compromised C2 server in 2026 revealed more than 1,570 linked victims.