Sangre de Cristo Electric Association
bd_066ac7934d5e4833 · schema v1 · pii pii-v2
Full breach record for Sangre de Cristo Electric Association →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
Sangre de Cristo Electric Association (SDCEA) has been informed that a substantial volume of sensitive information has been compromised. The affected information includes customer personally identifiable information, financial and payment data, utility account information, and information associated with the organization’s energy infrastructure and operational technology environment. The information includes details concerning electrical distribution infrastructure, substations, transformers, feeders, operational systems, renewable-generation assets, outage information, and SCADA/EMS-related environments. The compromise data also include highly sensitive authentication and security information, including control-system credentials, API keys, and OT security configurations. We previously proposed resolving the incident through a peaceful and confidential process. According to our account, negotiations were subsequently discontinued after SDCEA CEO Jon Beyer indicated that the organization had decided to end discussions. As a result, we are issuing this public statement concerning the incident. In addition, we will take further disruptive actions to ensure that, in the future, those responsible for making these decisions approach the security of the resources entrusted to them—including the people within their area of responsibility—with greater awareness and seriousness.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 1, 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.