Kenaitze Indian Tribe
Incident posture
Linked entities
- Victim
- Kenaitze Indian Tribe
- Threat actors
- 0 actors
- Sources
- 1 source
Timeline
Summary
The Kenaitze Indian Tribe notified 9,319 individuals after discovering suspicious network activity and determining that an unauthorized third party accessed its systems for several days. During the intrusion, files on compromised portions of the network may have been accessed or acquired, and a subsequent review confirmed exposure of first and last names, dates of birth, Social Security numbers, driver’s license numbers or state IDs, financial account numbers, health insurance information, and medical information. Affected individuals began receiving notifications after the review was completed.
Motives
Detailed motive labels are available to members.
TTPs
Detailed technique labels are available to members.
Description
The Kenaitze Indian Tribe in Alaska notified 9,319 individuals about a data security incident that exposed some of their protected health information. Suspicious activity was identified within its network on July 27, 2026. The investigation concluded that an unauthorized third party had access to its network between July 16, 2026, and July 27, 2026. During that time, files on the compromised parts of the network may have been accessed or acquired. The review of the affected data was recently completed. The incident was disclosed alongside breach announcements from Paylogix, the Center for Bone and Joint Surgery of the Palm Beaches, and Wichita Family Dental.
It has been confirmed that the exposed data includes first and last names, dates of birth, Social Security numbers, driver’s license numbers or state IDs, financial account numbers, health insurance information, and medical information. The affected individuals started to be notified on September 25, 2026. The notification covered individuals whose protected health information was potentially accessed during the unauthorized network intrusion. The tribe completed its review of the affected files before issuing notifications.
Sources
Sources available to members: 1 source.