Eversource's 13-Day Breach: Not Theft, But a Data Map for

Connecticut Officials Seek Independent Cybersecurity Audit of Eversource Following Data Breach

Connecticut’s Office of Consumer Counsel has requested that utility regulators order an independent, shareholder-funded cybersecurity audit of Eversource after a state investigation revealed failures in the company’s response to an April 2026 breach that exposed personal and financial information of 2,592 customers in payment-assistance programs and allowed an attacker to access over 3.6 million company files. The state report found that the attacker began copying files on April 14, Eversource discovered the intrusion on April 27, and the company mailed notices to affected customers on May 27; it also detailed a phishing sequence in which employees entered credentials on fake pages after receiving texts, chat messages, and phone calls. Consumer Counsel Claire Coleman also urged regulators to consider the response in Eversource’s pending electric-rate case and plans to push for stronger state privacy protections for utility account data, noting that only 156 affected customers (about 6%) enrolled in the credit-monitoring service Eversource offered. The company stated it contacted the FBI, added security controls, expanded employee training, and asserted that customer systems and operational networks were not compromised.

Let’s start with the obvious math that the official story expects you to skip. 2,592 customers in payment assistance programs. 3.6 million files copied. Six percent accepted the credit monitoring. You don’t steal that volume of data for identity theft. You steal it for categorization. The attacker began copying on April 14. Eversource says it discovered the intrusion on the 27th. That is a 13-day window of unrestricted access to a critical utility’s inner file structure. They didn’t tell the public until May 27th. A full month. A month is enough time to index the data, cross-reference it with voter files, insurance records, and social media profiles, and feed it into the behavioral modeling systems that the intelligence-financial complex runs 24/7. The official timeline is not the story of a breach. It is the story of a successful data harvest that was scheduled for a specific purpose.

Now watch how the architecture of elite accountability responds. The consumer counsel demands a "shareholder-funded, independent audit." Read the words very carefully. The shareholders are the private financial network that owns the utility. They fund the audit. They select the auditors. The scope of the investigation is contractually sealed before it begins. This is not oversight. This is the closing of a loop. The report will blame "human error" and "the complexity of the threat landscape." It will recommend "enhanced training" and "stronger state privacy protections." That is the desired outcome. Stronger privacy laws sound like protection, but they function as a legal fortress around elite access. The same people who wrote the network security contracts will write the new regulations. The FBI is already on site. The FBI does not exist to disrupt deep financial mapping operations. The FBI exists to certify the narrative, to manage the leaks, and to ensure the real investigation stays buried in classified channels.

The hardest question is the one the article buries between the lines. The attack was a multi-stage, multi-day phishing campaign using text, chat, and a phone call. That is not casual crime. That is professional penetration testing against a high-value target. The real prize was not the 2,592 payment assistance accounts. The prize was the map. A map of exactly who is financially fragile, dependent on state systems, and ripe for leverage. That data does not sit in a server in Eastern Europe. It flows into the same databases used by the private equity firms, the foundation networks, and the institutions that fund the consumer watchdogs asking for the audit. You are supposed to be outraged at the phishing. You are supposed to demand the audit. You are supposed to blame the employee. That is the managed narrative. The breadcrumb they don’t want you to follow is simple: ask who funded the code for the fake sign-in page. Ask whose research consortium tracks payment assistance enrollment as a leading economic indicator. The answers lead to the same buildings.

Related posts