Urgent.News

What's breaking now, across thousands of outlets.

Tech

[Insight] Hackers Did Not Target the Banks’ Vaults — The Path of Attack Has Changed

On October 3, financial authorities in Seoul stepped up their response to a series of cyber intrusions and personal data leaks that have spread from South Korea’s major banks to savings banks and consumer finance companies. But the more important question is not how many financial institutions have

Recent cyber intrusions and data leaks affecting major banks, savings banks, and consumer finance companies in South Korea have shifted the focus away from core transaction systems to peripheral systems connected to the internet. Financial authorities have initiated emergency meetings to address the issue, with the Financial Services Commission (FSC) convening a meeting on October 4 at the Government Complex Seoul.

Key affected institutions include Shinhan Bank, KB Kookmin Bank, Hana Bank, BNK Busan Bank, Woori Bank, NH NongHyup Bank, Yegaram Savings Bank, and Hyundai Capital. Despite no evidence of a single threat actor, investigators are scrutinizing the spread of attacks and how attackers found vulnerabilities in peripheral systems. The FSC has emphasized the importance of identifying all IT assets and services accessible from outside networks, reviewing authentication and access controls, and minimizing unnecessary exposure of information.

While the possibility of AI involvement has been raised, it remains premature to label the incidents as an "AI attack on the financial sector."

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

Read the original at koreaittimes.com →

More in Tech

ORA-00257: The Database Stopped Accepting Writes. The Archiver Is Stuck.

The pager goes off at 3 a.m.: the application is frozen. Every screen that tries to save hangs, and the ones that time out come back with ORA-00257: archiver error. Connect internal only, until freed.

  • Database stopped accepting writes due to ORA-00257 archiver error
  • Archiver process stuck because archived logs not being removed
  • Issue resolved by freeing up space in Fast Recovery Area (FRA)

More from Saturday 3 October →