The Free AI Tool That Just Hacked Seven Banks: The Skill Floor Has Disappeared

Published 9 October 2026 · Updated 19 October 2026

I spent the weekend watching a story unfold out of South Korea that should worry anyone who works in security or runs a business that handles customer data. Seven South Korean banks and lenders were breached in a coordinated campaign that, by reported estimates, exposed around 68,000 customer records. The tool used? A free, open-source AI penetration testing system called ARTEX that anyone can download from GitHub.

Let me be clear about why this matters more than most breach stories I cover. This is not about a sophisticated state-sponsored advanced persistent threat. This is not about a zero-day exploit that took years to develop. This is about an open-source tool developed in China that, CrowdStrike assesses with moderate confidence, a financially motivated attacker picked up and pointed at internet-facing banking portals. The AI did the rest.

What is ARTEX?

ARTEX is an autonomous penetration testing system built on large language models. It can conduct reconnaissance, identify vulnerable login endpoints, launch attacks, and verify results without continuous human direction. It was published as open source on GitHub.

The tool itself is not an AI model. It is more like a harness that connects to external LLMs and directs them at targets. In the South Korean attacks, analysis of the exposed files indicates the ARTEX instance used DeepSeek v4.1-flash as its main model, and CrowdStrike found Claude Code session logs, ARTEX configuration files and Claude memory files in an exposed directory on the attacker’s infrastructure.

The campaign ran from late September to early October 2026. At one bank, the attacker breached a loan progress inquiry service used by financial brokers. At another, they compromised an employee mobile work-support system.

The skill floor just collapsed

Here is the part that keeps me up at night. Traditional credential-stuffing campaigns required a competent attacker to manage bot infrastructure, rotate proxies, handle authentication challenges, and analyse results. ARTEX automates the entire attack loop. What previously required a skilled operator now requires someone who knows enough to point the tool at a target and wait.

The tool’s origin is irrelevant because it is now public. The genie does not go back in the bottle.

The Korea Financial Security Institute confirmed the ARTEX link after tracing attack IP addresses and server logs from Shinhan Bank, the first institution to report a breach. But attribution is murky. Oasis Security, tracking exposed infrastructure through its AGATHA platform, identified 359 unique IP addresses globally associated with ARTEX-related activity. The dominant hosting footprint was in the United States (65.7 percent), not China (14.8 percent). Anyone, anywhere, can run this tool.

The attacker left their resume in the command history

In one of the more bizarre turns in this investigation, CrowdStrike discovered that the attacker’s Claude Code session histories and configuration files were stored in open directories on the Hong Kong-based server. The files included the threat actor asking Claude to draft a security researcher resume using personal details: a 26-year-old from Guangdong, China, who studied at South China University of Technology.

The same session history shows the attacker asking Claude where threat actors typically sell Korean data breach information and asking for assistance finding Korean Telegram data sales groups. It is like watching someone build a career portfolio out of a crime scene.

The developer of ARTEX, Autumn-27, has since taken the project closed source, releasing a statement that the malicious attacks had nothing to do with them. “ARTEX was originally designed for the purpose of learning and research.” Of course it was. So was every other dual-use tool in existence.

What this means for the rest of us

South Korea activated a round-the-clock cybersecurity emergency and financial authorities launched probes into all seven affected institutions. But the lessons here apply everywhere.

First, agentic AI attack tools change the economics of offensive operations. The cost of launching a competent multi-vector attack just dropped to zero. Second, detection windows of 18 to 43 hours are not going to cut it when AI tools can adapt faster than humans can respond. Third, the open-source nature of these tools means attribution is harder, not easier, because the same software can run from servers in any country.

The ARTEX campaign is not an isolated incident. CrowdStrike also found that in July 2026, a different threat actor used Generative AI and LLMs from major providers to target software supply chains, including modifying open-source packages to implant backdoors. This is a pattern, not a one-off.

For security teams, the practical response starts with basics that are too often neglected. Lock down internet-facing services. Remove default credentials. Monitor for unexpected access to loan processing and employee support portals. These are not sophisticated defences. They are the kind of hygiene that most organisations still get wrong.

For the rest of us, the message is simpler. If you bank with an institution that still runs internet-facing portals on legacy authentication, start asking questions. The AI attack surface is not theoretical anymore. It is live, it is free, and it worked.


Update 9 October 2026: The developer of ARTEX has taken the project closed source following the South Korean attacks. Researchers at Oasis Security have identified 359 IP addresses associated with ARTEX deployments globally. South Korean police are investigating but have not attributed the attacks to any specific group or state.

“Systems connected to the external internet with relatively weak authentication are now exposed to automated attacks using AI. This is not a future risk. This is what happened last week.” — Professor Son Kyu-sik, Hanyang Cyber University

Correction (19 October 2026): An earlier version named the tool’s developer, described its origin as a Baidu challenge, listed additional AI models and intrusion durations, and quoted a Korean academic. We could not verify these details and have removed them. The record count is now described as a reported estimate.

Sources

Attribution is CrowdStrike’s moderate-confidence assessment. No customer financial losses had been confirmed at the time of writing. Commentary is the author’s analysis.

Related Reading

How this analysis is researched, sourced and corrected: Editorial standards and corrections. Spotted an error? Contact Philip Hall.

Subscribe

Related articles

A Trusted AI Tool Was Weaponised: Inside the Trojanized Claude Code Extension Attack

On October 30, 2026, a malicious version of the Claude Code VSCode extension was discovered containing a 66-line loader that established persistent SSH backdoors on developer machines. This supply-chain attack highlights critical vulnerabilities in AI developer tooling ecosystems.

DEBATE: Will AI End Capitalism in 2 Years? The Ex-Google Prediction Dividing the World

A former Google X executive predicts AI will end capitalism in 2 years. I dug into the actual data. The answer is more complicated than either side wants to admit.

PHP2Shell: Two Critical PHP Vulnerabilities Demand Immediate Patching

Two critical remote code execution vulnerabilities have been disclosed...

PHP2Shell: Two Critical Bugs, One Unavoidable Truth

# PHP2Shell: Two Critical Bugs, One Unavoidable Truth The PHP...
Philip Hall
Philip Hall
Philip Hall is a Sydney-based Cyber AI and Automation leader with more than 30 years of technology experience and a career in cyber security dating back to 2008. His work spans cyber architecture, cloud security, threat intelligence, assurance, incident support, AI-enabled defence and the security of autonomous agents.