CenterPoint Energy Confirms Breach as Hacker Claims 7.5M Files
The utility, serving about 7 million customers in four US states, told the SEC customer data was taken. A hacker claims 7.49 million files.
US utility CenterPoint Energy has confirmed that an unauthorized party obtained personal information belonging to some of its customers, Breached.Company reports.
What we know
- CenterPoint disclosed the incident in an SEC Form 8-K dated September 14, 2026, after becoming aware of an online post by a third party claiming to possess a customer data set (Reuters).
- A hacker using the alias "4d722e4d656f77" claims on a crime forum to have stolen 7.49 million customer files. CenterPoint has not confirmed that number publicly (BleepingComputer).
- The company serves about 7 million electricity and gas customers in Indiana, Minnesota, Ohio and Texas, employs roughly 8,300 people and generates over $9.3 billion in annual revenue (BleepingComputer).
- Power and gas services were not disrupted. CenterPoint said it does not currently believe the incident is reasonably likely to have a material impact on its financial condition (StockTitan).
Timeline of the breach
CenterPoint's SEC filing and subsequent reporting give a rough sequence of events. On September 12, 2026, a threat actor posted on a popular cybercrime forum claiming to have obtained nearly 7.5 million customer records, making a 2.5 GB archive available for download and threatening that "next time we won't simply pull data, we'll start attacking the main infrastructure" (SecurityWeek). CenterPoint says it became aware of the post in September, activated its cybersecurity incident response protocols, and brought in outside cybersecurity experts to investigate. On September 14, it filed the 8-K confirming that an unauthorized third party had obtained personal information belonging to a portion of its customers through an external-facing system.
How the attacker says they got in
According to the threat actor who spoke with BleepingComputer, the data was pulled by iterating through millions of customer IDs on CenterPoint's public-facing API, which allegedly lacked rate limiting, web application firewall protection, or other defenses against automated, large-scale scraping (BleepingComputer). The attacker claims the exposed data includes names, phone numbers, service and billing addresses, account numbers, billing amounts, and partial Social Security numbers. CenterPoint's own filing does not confirm the exact data types or number of affected customers, saying only that the investigation is continuing.
If accurate, this style of attack — sometimes called "enumeration" or "scraping via insecure direct object references" — is one of the more common and avoidable causes of large breaches. It does not require breaking encryption or planting malware; it simply exploits an API that will return a customer's record for any valid-looking ID number, without checking whether the requester is authorized to see it or limiting how many requests they can make.
Why it matters
Utility customer records typically include names, home addresses, account numbers and sometimes payment details — useful for fake "your power will be cut off" scams. And because utilities run critical infrastructure, any intrusion raises the question of how well customer systems are separated from the systems that keep the lights on. CenterPoint has stressed that electric and gas delivery were never disrupted, which suggests at least some separation between customer-facing IT and operational technology (OT) systems that run the grid — a distinction regulators and security researchers increasingly scrutinize after incidents at other utilities and infrastructure operators worldwide.
This is also not the first time CenterPoint has faced scrutiny over a hacking claim, according to SecurityWeek, underlining that utilities — which hold large, stable databases of long-term customers — are attractive, repeatable targets for data thieves.
Regulatory and disclosure context
Since December 2023, SEC rules have required publicly traded companies to disclose cybersecurity incidents they determine to be material within four business days of that determination, which is why CenterPoint's confirmation came via an 8-K filing rather than, or in addition to, a conventional press release. The filing was classified under Item 8.01 (Other Events), a category companies commonly use for incidents they consider worth disclosing to investors even when they have not yet concluded the incident is "material" in the formal securities-law sense.
CenterPoint said it has reported the matter to law enforcement, is working to define the scope of affected customers and data, and will notify customers and regulators as legally required. It added that it expects its cybersecurity insurance to offset at least some of the related costs.
What customers should do
- Be suspicious of calls or texts demanding immediate payment to avoid disconnection. Utilities do not demand gift cards or crypto.
- Pay only through the official app, website or number on your bill.
- Watch for an official notice explaining what data of yours was involved, and read it carefully — it may specify dates and data types that the public reporting does not.
- If your Social Security number may have been exposed, consider placing a free fraud alert or credit freeze with the major credit bureaus.
- Treat any email or text that references your CenterPoint account, outstanding balance, or service address with extra suspicion, since scammers often weave real breach details into phishing lures.
- Check whether your email address appears in other breaches too, since criminals often combine data from multiple leaks to build more convincing scams.
What readers should do
- Verify before you pay. If anyone contacts you claiming to be from CenterPoint and demanding urgent payment, hang up and call the number printed on a past paper bill or on the utility's official website.
- Monitor your accounts. Watch bank and card statements for unfamiliar charges in the weeks after a breach like this.
- Freeze your credit if you believe your Social Security number was exposed — this is free in the United States and prevents new accounts being opened in your name.
- Keep records. Save any breach notification letter you receive; you may need it to dispute fraudulent accounts later.
- Report suspicious contact to the Federal Trade Commission at identitytheft.gov if you believe you have been targeted using breached CenterPoint data.
Background: CenterPoint Energy and its customer base
CenterPoint Energy is a Houston-based, publicly traded utility holding company (NYSE: CNP) that provides electricity delivery, natural gas distribution and, through its regulated subsidiaries, power generation across several US states. Its service territories include the greater Houston area, parts of Indiana, Minnesota and Ohio. As a regulated monopoly utility in most of these markets, CenterPoint holds long-term, largely non-removable customer records — residents typically cannot switch providers the way they might with a bank or retailer, which makes stolen utility data especially durable and valuable to scammers who can expect a name and address to stay linked to the same household for years.
The growing pattern of utility-sector breaches
CenterPoint's disclosure fits into a broader pattern of attacks against utilities and critical-infrastructure-adjacent companies. Energy, water and telecom providers have increasingly been targeted not because their grids are always the end goal, but because their customer databases are large, stable and often protected by less mature cybersecurity programs than banks or large tech firms. Security researchers have repeatedly flagged weakly secured customer-facing APIs — the same category of flaw alleged in the CenterPoint case — as one of the most common, and most preventable, causes of large-scale data theft across many industries in recent years.
Expert perspective on API security failures
The technique described by the alleged CenterPoint intruder — enumerating sequential or predictable customer IDs against a public API with no rate limiting — is sometimes referred to by security professionals as a "broken object level authorization" (BOLA) flaw, consistently ranked by the Open Web Application Security Project (OWASP) as the single most common vulnerability class in modern APIs. Unlike more sophisticated attacks involving malware or credential theft, this type of flaw can often be exploited with simple, automated scripts, and the lack of a web application firewall or rate limiting is what allows an attacker to pull millions of records before being noticed, rather than being blocked after a handful of suspicious requests.
Sources & Verification
Additional reporting
- Breached.Companybreached.company
- Reutersreuters.com
- BleepingComputerbleepingcomputer.com
- SecurityWeeksecurityweek.com
- StockTitanstocktitan.net



