Urgent.News

What's breaking now, across thousands of outlets.

Tech

Personal data of some 24,000 KEPCO employees leaked

The personal information of some 24,000 employees at the state-run Korea Electric Power Corp. (KEPCO) has been leaked, the company said Sunday, the latest in a series of personal data leaks at corporations. "We became aware that the personal information of employees was exposed on an external web site at around 3:59 p.m. Thursday," KEPCO said in a statement. The leaked information includes their…

Personal data of some 24,000 KEPCO employees leaked

Personal data belonging to around 24,000 employees at state-run Korea Electric Power Corp. (KEPCO) was leaked, the company announced on Sunday. This marks the latest in a series of personal data breaches affecting corporations. KEPCO discovered that the information, encompassing names, job positions, and telephone numbers, had been exposed on an external website around 3:59 p.m. on Thursday. According to the company, the leaked data did not include sensitive information like resident registration numbers.

KEPCO has since notified the affected employees and removed the leaked data by midnight on Friday. The company assured customers that their information stored in a separate system remained secure. This incident follows several recent data leaks at major financial institutions, including Hana Bank, KB Kookmin Bank, and Shinhan Bank, which were attributed to hacking attacks.

A KEPCO official stated that the company is investigating the cause of the incident, emphasizing that the data breach appears unrelated to artificial intelligence.

Written by urgent.news from The Korea Times's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at koreatimes.co.kr →

More in Tech

MockMate: a free interview coach for [friend's name] that runs on my own laptop

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend What I Built Ragul is preparing for cloud and data analytics jobs in Tamil Nadu, and so am I, which means we both know…

  • MockMate is a free interview coach app for interview preparation
  • Runs on user's laptop using open-weight model Qwen2.5:7b
  • Provides scoring, feedback, and tracks progress offline

DayBuddy — a daily companion I built for my friend Yashu

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend What I Built DayBuddy is a daily companion I built for my friend Yashu.

  • DayBuddy is a daily companion app created for Yashu by Gautam.
  • Yashu struggles with daily routine, often sleeping late, skipping meals.
  • App personalizes plans, adjusts based on Yashu's check-ins.

Next.js ~Cache Systems~

The cache systems of Next.js(especially App Router) are made to allow you to optimize performance and minimize data transfer costs.

  • Next.js has four cache layers: Request Memoization, Data Cache, Full Route Cache, and Router Cache.
  • Request Memoization combines GET fetch requests on server side, preventing redundant API calls.

Authenticating GitHub Actions to AWS Without Access Keys (OIDC)

While being mentored on GitHub Actions recently, my mentor told me to use OIDC to authenticate to AWS. I honestly had no idea you could authenticate without a static access key, so I dug deeper.

  • OIDC enables GitHub Actions to authenticate with AWS without access keys
  • Set up involves creating an OIDC provider, IAM role, trust policy, and GitHub Actions workflow
  • Temporary AWS credentials expire after each workflow run, enhancing security

More from Sunday 4 October →