security research (CrowdStrike Intelligence report, Oct 7 2026, US time) · official-adjacent (Korea Financial Security Institute, via The Herald Business) · media (The Korea Times; Aju Press)

A hacker used an AI break-in agent on South Korea’s banks, then left the AI logs on an open server

Origin Lane: aiSouth Korea (financial sector targets) · online operation, no map location

DATA: The Herald Business

A person, not a rogue machine, ran this one. Korea’s Financial Security Institute says the AI did not act on its own: “A hacker used the AI as a tool.” No government or named hacking group has been blamed. CrowdStrike says the attacker, likely a Chinese speaker chasing money, spent about two weeks using ARTEX, a recently released open-source AI agent for break-ins, against the back-office systems of South Korean banks, and walked out with customer data. What gave it away was carelessness: open folders on the attacker’s own servers held their AI session histories.

Key facts

Human in the loop
“The AI did not act independently without human involvement. A hacker used the AI as a tool” (Korea Financial Security Institute official, via The Herald Business)
Who
Not attributed to any state or named group. CrowdStrike assesses with moderate confidence a Chinese speaker, financially motivated, based on the Chinese-built tool and Chinese-language prompts
No online banking hit
Every attack hit internal employee or partner-facing systems, not customer internet or mobile banking (Financial Security Institute, via The Herald Business)
The AI agent
ARTEX, a recently released open-source agentic penetration-testing tool developed in China, run mainly on DeepSeek v4.1-flash, with GLM-5.3 (Zhipu AI) and Grok 4.6 used in other Claude Code sessions (CrowdStrike)
Window
Late September to early October 2026 (CrowdStrike)
Banks named
Shinhan, KB Kookmin, Hana, Yegaram Savings Bank and BNK Busan Bank (The Korea Times). Aju Press counts seven financial companies hit
All facts (10)
Data exposed
Shinhan: 25,729 people via a loan inquiry service used by brokers (names, phone numbers, annual income, loan limits). KB Kookmin: 119 customers. Hana: 89 records. BNK Busan: 11 contract workers (The Herald Business; The Korea Times)
How it surfaced
Open directories on attacker-controlled servers, one in Hong Kong, held Claude Code session histories, Claude memory files and ARTEX configuration files (CrowdStrike)
Selling the haul
The attacker asked Claude where Korean breach data is usually sold and for help finding Korean Telegram data-sale groups (CrowdStrike)
Identity
One session asked Claude for a security-researcher résumé listing the attack results. CrowdStrike says personal details in that prompt likely belong to the attacker but cannot yet be definitively linked. Doom Signals is not printing them

This activity demonstrates how AI tooling can enable a financially motivated threat actor to conduct multiple intrusions within a short time span.

CrowdStrike Intelligence, 7 Oct 2026

Note

CrowdStrike Intelligence published a report on Oct 7 (US time) on a campaign against South Korean financial organizations that ran from late September to early October 2026 and ended with stolen data. CrowdStrike has not tied it to any named group or state. It assesses, with moderate confidence, that the attacker is a Chinese speaker motivated by money, based on the Chinese-built tool and Chinese-language prompts. A Financial Security Institute official told The Herald Business that AI was used but did not act on its own: “A hacker used the AI as a tool.”

The institute traced attack IPs and server logs at Shinhan Bank, the first to report a breach, and told The Herald Business it found clear evidence that ARTEX was used. Every attack hit internal employee or partner-facing systems, not customer internet or mobile banking. Shinhan says 25,729 people had names, phone numbers, annual income and loan limits exposed through a loan inquiry service used by brokers. KB Kookmin reported 119 affected customers, Hana Bank 89 records and BNK Busan Bank 11 contract workers. Police and financial regulators are investigating.

CrowdStrike describes ARTEX as a recently released open-source agentic penetration-testing tool developed in China: software that uses a large language model to probe systems for weaknesses and act on them. It found an ARTEX instance on one attacker-controlled server and, on a second server in Hong Kong, open directories holding Claude Code session histories, Claude memory files and ARTEX configuration files. The ARTEX instance ran mainly on DeepSeek v4.1-flash, likely bought through a third-party reseller, and the attacker also used GLM-5.3 from Zhipu AI and Grok 4.6 in Claude Code sessions. A Chinese-language instruction file told the model how to carry out the break-ins.

The logs show the attacker routing through nine proxy IP addresses, asking Claude where Korean breach data usually sells, and asking for help finding Korean Telegram data-sale groups. In one session the user asked Claude for a security-researcher résumé listing the results of the operation. CrowdStrike says the personal details in that prompt likely belong to the attacker but cannot yet be definitively linked, and Doom Signals is not printing them.

It is the second case in a week. SOCRadar’s CyberXero report (Oct 6) showed a Russian-speaking criminal running dozens of Claude Code agents against Ukrainian energy firms; this one shows a single operator using an open-source Chinese AI break-in tool against Korean banks. Both were found only because the attacker left AI logs exposed. CrowdStrike expects attackers to keep adding AI tooling to work faster.

Why it matters

This is the second open-server leak in a week showing one person steering AI agents at real institutions: first Ukraine’s energy companies, now South Korea’s banks. The tool is open source, the model is cheap, and this attacker was sloppy enough to leave the notebook open. The careful ones don’t show up in reports like this.

Sources

Primary + secondary attribution as listed.

Daily board · Archive

Doom Signals desk · About · Contact · Corrections. Spotted an error? Write the desk; fixes go on the public log.