Urgent.News

What's breaking now, across hundreds of outlets.

Tech

CrowdStrike finds possible bank hacker's CV among exposed AI logs

Suspected Chinese speaker used Claude Code and agentic pentesting tool ARTEX in attacks on South Korean lenders

CrowdStrike finds possible bank hacker's CV among exposed AI logs

CrowdStrike researchers discovered AI session logs that may identify a hacker targeting South Korean banks. The logs contained operational details and a resume request linking the attacker to YY, a Chinese individual with conflicting age information. At least five banks, including Shinhan Bank and KB Kookmin Bank, were affected.

The attackers breached a loan progress inquiry service and a mobile work-support system. References to YY appeared in AI sessions associated with ARTEX, an open-source penetration-testing tool developed in China. Researchers found session histories, configuration files, and AI memory files on a server in Hong Kong. This incident marks the growing use of AI in cyberattacks, enabling threat actors to conduct multiple intrusions quickly.

Police are investigating the attacks, and legislators plan to audit the major banks for cybersecurity lapses.

Rewritten by urgent.news; may contain errors — check the original.

Source: theregister.com

This story

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

Every outlet that reported this, and when →

Read the original at theregister.com →

Report a problem with this story

More in Tech

Why a square picture needs 24 x 30 stitches: gauge math for a crochet chart tool

I built a small, free, browser-only tool that turns an image into a single-crochet color chart. This post covers the one idea that makes it more useful than a plain pixelator: gauge.

  • Square pictures require 24 x 30 stitches due to gauge math
  • Tool converts images to single-color crochet charts
  • Limitations include size and complexity constraints

Treat Sales Handoffs as Explicit Workflow States

Treat Sales Handoffs as Explicit Workflow States A sales workflow should not treat “notification sent” as equivalent to “owner accepted.” Those are separate system states, and modelling them…

  • Distinguish between notification sent and owner accepted as distinct workflow states.
  • Create explicit model: RECEIVED → VALIDATED → ROUTED → ACCEPTED → NEXTACTIONRECORDED.
  • Implement retries with idempotency keys to avoid duplicate records.

We migrated the receiver but forgot the return trip

We migrated the receiver but forgot the return trip Same incident, different lesson. (If you're counting, this is the day our infrastructure decided to teach a whole curriculum — see also your webhook…

  • Receiver migrated to new server successfully
  • Return connection to processor not established
  • Sync job recreated within five minutes to resolve issue

More from Thursday 8 October →