Cyber & AI intelligence
Briefs indexed3981
Issues37
Published Mondays07:30 CT
▣ Breach KEPCO-CUSTOMER-PAY 2026-11-22

KEPCO: 1.52 Million Customer Payment and Procurement Records Leaked

"Korea Electric Power Corporation (KEPCO), South Korea's state-owned electricity utility, said on 22 November 2026 that about 1.52 million records were leaked from two of its systems: the KEPCO ON customer service…"

Korea Electric Power Corporation (KEPCO), South Korea's state-owned electricity utility, said on 22 November 2026 that about 1.52 million records were leaked from two of its systems: the KEPCO ON customer service platform and the SRM electronic procurement system. The leaked data includes the bank account and card numbers customers use to pay their electricity bills, plus resident registration numbers. This is a second and much larger breach. In October, KEPCO disclosed a leak of employee data that eventually reached 35,528 people. Financial News reports the 1.52 million total from KEPCO's announcement, and The Herald Business rounds it to about 1.5 million. KEPCO's published per-system counts add up to roughly 1,520,248. KEPCO has not said who was behind the attack or how they got in.

What Happened

Financial News and The Herald Business both report that KEPCO found the breach on Friday, 20 November. It then blocked external access and temporarily suspended some services. The Herald Business says KEPCO cut off external IP access and suspended overseas services in particular. KEPCO asked the police to investigate. It is working with the National Intelligence Service, the Ministry of Climate, Energy and Environment's cybersecurity center and outside security experts to find out whether more data leaked and how much damage was done.

KEPCO is notifying affected people individually. In an apology issued on 22 November, it said it had found no cases of secondary damage so far. It also said it would work with the financial authorities to check whether the leaked financial data has been misused.

A possible dark web link that nobody has confirmed. On 19 November, the day before KEPCO says it found the breach, a user called "Noiem" posted on the DarkForums cybercrime forum claiming to hold KEPCO data. DailySecu, Osegi and Brinztech reported the post. It was titled with KEPCO's name and its kepco.co.kr domain and advertised a dataset labelled "560M CSV". Buyers were directed to a Proton Mail address. The supplier, bid-price and contract data it listed matches the kind of work SRM handles. However:

The timing suggests a link, but whether the listing and KEPCO's confirmed breach are the same incident is still unknown.

What Was Taken

KEPCO's breakdown, as reported by Financial News and The Herald Business:

KEPCO ON customer platform: 650,487 customers, 12 data fields - Customer numbers, names, resident or foreign registration numbers - Phone numbers and addresses - Bank names, account numbers, account holder names - Card issuers, card numbers, cardholder names - Billing information

SRM electronic procurement system: about 870,000 users - 426,827 corporate representatives, 4 fields: names, resident or foreign registration numbers, email addresses, company addresses - 442,934 KEPCO and partner company employees, 6 fields: names, affiliations, employee ID numbers, mobile numbers, email addresses, office phone numbers

KEPCO ON is the most serious exposure. It puts national ID numbers, home addresses and payment account details together in one record. With that combination, criminals can pose as KEPCO in phishing, take over accounts and try fraud with stolen card details. No reports say that card expiry dates or security codes were taken.

What the forum seller claimed. The Noiem listing also offers procurement data that KEPCO has not confirmed as leaked: - About 950,000 supplier records - 401,951 bid reserve-price records, which Brinztech says are valued at 153.9 trillion won in total - 26,859 private contract records - Entries for military and government suppliers. DailySecu lists 3,124 military supplier records and 12,036 government supplier records.

The listing's figures for supplier ID-number records also vary between reports. DailySecu read two figures in the post, 405,080 and 366,896. Brinztech reports 410,670. Brinztech notes that the listed row counts add up to about 2.8 million, so "560M" probably refers to file size rather than record count. None of this procurement data has been verified.

Why It Matters

The Attack Technique

Nobody knows yet. KEPCO has not said how the attackers got into KEPCO ON or SRM, how long they had access, or whether the two systems were breached separately or through shared infrastructure. Its decision to cut off external and overseas access suggests it believes the attack came in from outside, but it has not said so. The forum post gives no technical details. For the October incident, investigators were looking at both outside hacking and a leak through a partner company (Aju Press, Yonhap Infomax), but that cause has not been settled either.

What Organizations Should Do

  1. Check what data you hold in customer portals. Do not keep full account or card numbers and national ID numbers in the same system as general customer service data. Use tokenization through your payment processor, and mask or encrypt ID numbers at the field level.
  2. Set alerts for large exports from procurement and supplier portals. Systems like SRM hold valuable bid and supplier data and are reachable from the internet by thousands of outside users. Alert on bulk queries, unusual export volumes and access from unexpected countries.
  3. Watch dark web forums for your domain. In this case a listing naming kepco.co.kr was public a day before the breach was officially found. Searching forum posts for your brand and domains can give you that day back.
  4. Treat repeat incidents as a sign of deeper problems. After any breach, review everything connected to the affected environment, including partner and supplier access, cloud storage and shared credentials, not just the first system found.
  5. Get ahead of impersonation scams. Tell customers plainly that you will not ask for payment details or verification by text or phone. Publish an official way to check whether their data was affected, and work with banks and card issuers to flag at-risk accounts.
  6. If you work with KEPCO: expect targeted phishing that uses real contract and contact details. Confirm payment-change and invoice requests through a separate channel. Korean customers who were affected can register their exposure with the Financial Supervisory Service's personal data exposure prevention system and block new phone activations in their name through M-Safer.

Sources: Electricity Bill Payment Account and Card Numbers Also Leaked From... | Korea Electric Power Corporation leaks about 1.5 million customers'... | KEPCO data leak claim on DarkForums, 592,585 records · Osegi | 단독 다크웹에 ‘한전 개인정보·입찰자료 확보’ 주장…전자조달시스템 SRM 관련 가능성 조사 필요 < 긴급속보 < 이슈 <... | KEPCO ES warns of possible personal data leak after DOUZONE BIZON h... | Korea Electric Power Corporation CEO Apologizes for Data Breach, Pr... | KEPCO Allegedly Breached as Actor Advertises 560M CSV Procurement D... | KEPCO Chief Apologizes for Data Breach, Debt Rises Despite 15 Trill...