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 have discovered AI session logs that may reveal the identity of attackers who breached South Korean financial institutions. Analyst Ashley Campion reported that the logs contained operational details and a resume-writing request, suggesting the prompt named "YY" could belong to the attacker. The attackers targeted at least five banks, including Shinhan Bank, KB Kookmin Bank, Hana Bank, Yegaram Savings Bank, and BNK Busan Bank.

The breaches occurred through a loan progress inquiry service and a mobile work-support system. The researchers found references to "YY" in AI sessions used alongside a recently released open-source penetration-testing tool called ARTEX, developed in China. The attackers also used a Telegram username linked to targeting a Chinese payment platform and Claude Code sessions looking for vulnerabilities in a Telegram-based NFT gift marketplace.

CrowdStrike Intelligence believes adversaries will likely continue experimenting with AI tooling to enhance their operational tempo and capabilities. Lawmakers have proposed summoning the heads of major commercial banks for a parliamentary audit on cybersecurity lapses.

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

Source: theregister.com

Other reports of this story

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 →