The Incident Board.

Documented AI security incidents.

Case 18ARTEX and Claude Code / South Korean banks

CrowdStrike links ARTEX and Claude Code artifacts to data theft at South Korean financial firms

CrowdStrike says exposed attacker infrastructure held ARTEX and Claude Code artifacts linked to data theft at South Korean financial firms. Its report does not map a recovered session to each theft.

Affected system
South Korean banks and lenders; loan inquiry pages, employee mobile systems and other side systems
Case status
Police and regulator investigations open
Sources checked

Overview

From about September 27 to early October 2026, attackers took customer and staff records from several South Korean banks and lenders through poorly protected side systems, such as a loan-broker inquiry page and an employee mobile app. CrowdStrike reported on October 7 that exposed infrastructure it assessed was likely responsible for the attacks contained Claude Code session histories, ARTEX configuration files and Claude memory files. Its artifacts show an ARTEX and Claude Code operation using DeepSeek and other model backends, but the public report does not name the victim firms or map a specific recovered session to each theft. Korean authorities separately described several exploited weaknesses, including missing authentication, inadequate device controls, unpatched web flaws and known vulnerabilities used to install malware and take logs. (CrowdStrike; Nocut News; FSC, October 4 meeting)

Status: under investigation by the National Police Agency and the financial regulators; no suspect is confirmed, and the Financial Services Commission (FSC), which on October 14 listed 16 financial firms with intrusions and about 100,000 leaked records, says it is still examining whether one actor hit all 16. Record updated November 6, 2026. Provisional severity: Serious (3/4), because sensitive personal data was taken from at least seven regulated firms, including some resident registration numbers, while the regulator found no account passwords or card numbers among the leaked data and no reported fraud losses through November 6; the incident is narrower in organizational breadth and demonstrated downstream harm than the Board's current Critical precedents. (FSC, October 14; FSC, November 6)

Reported impact

The firms that disclosed breaches in the first days, and that the financial authorities tied to shared attacker IP addresses, are Shinhan Bank, KB Kookmin Bank, Hana Bank, BNK Busan Bank, Yegaram Savings Bank, Welcome Savings Bank and Hyundai Capital. (Nocut News; Financial News)

Firm Reported data taken Source
Shinhan Bank About 25,000 customers' loan-application data (name, phone, annual income, calculated loan limit), including 66 resident registration numbers and 97 linking-information (CI) codes; reports give 25,727 or 25,729 MTN, relaying the bank's apology; Kyunghyang; Financial News
Yegaram Savings Bank About 40,000 customers' names, phone numbers and dates of birth (bank's estimate, still being checked) iNews24
KB Kookmin Bank 119 people: names, phone numbers, addresses, encrypted resident registration numbers; CEO Score reports 99 customers (including credit grade and overdue revolving-credit principal) and 20 current or former employees iNews24; CEO Score Daily
Hana Bank 89 people: resident registration numbers, names, addresses, email, phone numbers, employer iNews24
Welcome Savings Bank Up to about 2,200 corporate-customer records (company name, contact person, email, phone); Kyunghyang says more than 2,200 Financial News; Kyunghyang
Hyundai Capital 146 mortgage loan brokers' details, including resident registration numbers Financial News
BNK Busan Bank 11 outsourced developers' names, phone numbers, dates of birth, emails iNews24

Financial News added these up to about 66,000 people plus up to about 2,200 corporate records. That sum matches the figure of about 68,000 in later coverage: Weekly Kyunghyang gives about 68,000 records across the seven firms, and DW, citing Korean media, says "as many as 68,000 customers." The match is our inference from the arithmetic. The figure mixes customers, brokers, staff and company records, is a count of records reported in the first week, and was never an official total. On October 14 the FSC reported intrusions at 16 firms across banking, savings banks, mutual credit, lending, electronic finance, online lending and virtual assets, and about 100,000 leaked records across them (names, contact details, resident registration numbers, emails and other fields). It said the number of firms could grow and that whether the same actor was behind them is "under detailed investigation" (our translation); it has not said that one actor was behind all 16. (Weekly Kyunghyang; DW; FSC, October 14)

What happened

CrowdStrike says it found an ARTEX instance and an open directory on the server 38.244.50[.]120, including a CLAUDE.md file with a Chinese-language penetration-testing prompt. That file pointed to a Hong Kong server, where further open directories held Claude Code session histories, ARTEX configuration files and memory files covering late September to early October. CrowdStrike writes that "The ARTEX instance used DeepSeek v4.1-flash as the primary LLM backend, and the threat actor supplemented this LLM with GLM-5.3 (Zhipu AI) and Grok 4.6 for additional Claude Code sessions," and that the actor likely reached DeepSeek through a likely API reseller, xcai[.]pro. It also reports that the actor "asked Claude where threat actors typically sell Korean data breach information" and for help finding Korean Telegram data-sale groups. CrowdStrike names no victim; it says the targeted organizations overlap with industry reporting and that the number affected "remains unconfirmed." (CrowdStrike)

The report does not say how the actor obtained Claude Code, whether Anthropic accounts were used, or which model answered the requests it attributes to "Claude." Its own sentence places GLM-5.3 and Grok 4.6 inside "additional Claude Code sessions," so at least some sessions ran Anthropic's coding tool on other companies' models. Whether any Anthropic model processed intrusion or data-sale requests is not established in the public record. CrowdStrike assesses with moderate confidence that the actor is a Chinese speaker and financially motivated. It found personal details in one prompt but says it "cannot definitively associate these details with the threat actor"; a man reached by Reuters at the listed phone number said he had no knowledge of the matter. (CrowdStrike; Reuters via BusinessDay)

Korean evidence came first. On October 2, Genians Security Center reported the string "ARTEX-自主渗透試控制台" (Chinese for an autonomous penetration-test console) in the HTML titles of web servers used in the attacks. An anonymous Financial Security Institute official told Herald Business that tracing Shinhan Bank's logs and attacker IP addresses showed ARTEX traces, and added (our translation of the Korean) "It is true that the attack used AI, but the AI did not attack on its own without human involvement." Financial authorities told Korean media on October 5 that the same attacker's IP addresses turned up across the seven firms' incidents; the IPs used against the commercial banks differed from those used against the savings banks and Hyundai Capital, but the methods were similar. Woori Bank and NH NongHyup Bank reported blocked attempts with no data loss. (Kyunghyang, October 2; Kyunghyang, October 4; Herald Business; Nocut News; Korea JoongAng Daily)

How the boundary failed

Operator writing Chinese-language prompts (identity unconfirmed)
   |
   v
Claude Code sessions + CLAUDE.md pentest prompt        Models named by CrowdStrike:
ARTEX instance on 38.244.50[.]120  ------------------>  DeepSeek v4.1-flash (ARTEX backend, likely via reseller xcai[.]pro)
Hong Kong server as main infrastructure                 GLM-5.3 and Grok 4.6 (other Claude Code sessions)
   |                                                    [which model handled the "Claude" requests: not stated]
   v
Proxy infrastructure reported by CrowdStrike: 9 addresses in the ARTEX investigation
Separate FSS count reported by the press: 28 addresses in 12 countries across the broader inquiry
[the overlap between these two sets is not published]
   |
   v
Side systems at banks and lenders: loan-broker inquiry pages, employee mobile
work systems, a sales-support system, and a homepage with known flaws
   |
   v
Reported paths: unauthenticated or bypassable look-ups; missing device controls
or unpatched web flaws; known vulnerabilities followed by malware-assisted log theft
   |
   v
[attributed to CrowdStrike only] the operator asks where Korean breach data is sold; no sale confirmed

The exploited weaknesses were in systems operated by the affected firms. Financial authorities sorted the cases into three types (our translation of the Korean): inquiry services built so that loan applications or company-representative details could be looked up without identity checks; employee work-support services with missing mobile-device access control or unfixed web flaws; and a homepage where the attacker used known vulnerabilities to install malware and take log files containing customer data. Shinhan's leak came through a loan-broker inquiry service that needed no certificate login. The FSC's own summary names "systems used by employees and by outside personnel such as loan brokers and contractors" as the cause (our translation). (Nocut News; YTN; FSC, October 4 meeting)

How the attacker found valid records is described differently. Kyunghyang reports that the attackers fed random values into Shinhan's broker service to find valid customer numbers; YTN and Weekly Kyunghyang describe brute-force or credential-stuffing logins; Shinhan's account, as relayed by MTN, says access came through "an abnormal method that bypasses authentication" (our translation). The Financial Security Institute official said the attacker "did not take over the systems" but pulled data through look-ups (our translation). Banks with layered authentication, such as Woori and NH NongHyup, turned the same attempts away. (Kyunghyang; Weekly Kyunghyang; MTN; Herald Business)

The second boundary concerns coding-agent sessions and model backends that CrowdStrike says were used during the activity, including requests about where stolen Korean data is sold. The public report does not identify which model handled those requests, whether any model refused, whether provider safeguards applied, how the actor paid for or obtained access, or whether every backend was reached through its named provider. Hunt.io later reported that one exposed Claude Code configuration routed through Claude Code Router and xcai to DeepSeek rather than directly to the Anthropic API. A provider-safeguard failure is therefore not established. How much of each intrusion ARTEX automated, versus the operator, is also unknown; Weekly Kyunghyang notes that this remains for the police to determine. (CrowdStrike; Hunt.io; Weekly Kyunghyang)

Consequences

People whose data was taken face targeted phishing risk: the leaked Shinhan records pair names and phone numbers with income and loan limits, which regulators warned could make fake loan calls convincing. The FSC and FSS issued a consumer alert on October 6, which PIPC also posted, and set a one-month special response period with dedicated help desks and stepped-up fraud monitoring of affected customers. On November 6 the FSC said no cases of customer funds lost to voice phishing or smishing linked to the leaks had been reported, and it extended the special period to the end of December. (FSC alert; FSC, November 6)

Affected firms shut the exposed services and blocked attacker IPs. No attack-caused outage of customer banking was found in the sources reviewed; BleepingComputer's mention of outages is not supported by the official statements read. Its report of exposed "credit card information" at KB Kookmin also conflicts with KB's own description relayed by iNews24 and with the FSC's October 14 finding that no account passwords or card numbers had leaked; CEO Score reports credit grades and overdue revolving-credit principal among KB's leaked fields. (BleepingComputer; iNews24; CEO Score Daily; FSC, October 14)

The regulator ordered checks across the sector. By October 8, 555 firms had completed a 12-item checklist and 130 reported shortcomings, mostly missing patches and monitoring gaps. On November 5 the FSC announced a full review of external access points at about 580 firms, more frequent vulnerability assessments for large firms, and a planned Digital Financial Safety Act bill (our translation of the Korean name) for the first quarter of 2027. The ARTEX developer stopped public releases, though earlier copies remain in circulation. (FSC, October 14; FSC, November 5; Korea JoongAng Daily)

The FSC's later totals cover a broader wave. Its 16-firm list of October 14 adds DB Savings Bank, OK Savings Bank, KDB Capital, PFCT, Mouda, Brightfix, Streami, Prabang and the Korean Federation of Community Credit Cooperatives to the first seven. By November 3, 37 firms had reported 40 incidents with about 473,000 leaked records, and small crypto exchanges, electronic-finance firms and online lenders reported about 1 billion won in company-held funds stolen. The FSC attributes none of these totals to the ARTEX actor, and this record does not count them as its impact. (FSC, October 14; FSC, November 5)

Vendor response

Anthropic. No Anthropic statement on this case was found on its newsroom or threat-intelligence page, or in news searches through November 6. Reuters reported on October 8 that Anthropic did not immediately respond to a request for comment. No report of account bans tied to this case was found. (Reuters via BusinessDay; Reuters via Taipei Times)

DeepSeek, Zhipu AI, xAI and the reseller. No statement from DeepSeek, Zhipu AI or xAI about this case, and none from the operator of xcai[.]pro, was found in searches through November 6.

ARTEX developer. The developer said on October 8, in Reuters' translation, that because of "misuse of the tool" the project "will no longer be updated and will be converted to closed source." Reuters says the statement did not directly address the bank attacks. (Reuters via The Straits Times)

CrowdStrike. Adam Meyers, CrowdStrike's senior vice president of counter adversary operations, told reporters the case "allows one human to target many customers in a very short period of time using the power of AI." (Reuters via Taipei Times)

Affected firms. Shinhan Bank apologized, opened a lookup page for customers to check exposure and said it would compensate any loss in full. KB Kookmin and Hana told customers how to claim damages. Yegaram Savings Bank apologized and said it had blocked external IPs and suspended the service. These statements were read through Korean press, not on the firms' own sites. (MTN; CEO Score Daily; iNews24)

Official oversight

Checked November 6, 2026. Jurisdictions: South Korea (FSC, FSS, National Police Agency, PIPC, MSIT and KISA); China (foreign ministry); United States (no action found).

Authority Action on this incident Status / basis Next step Official source
Financial Services Commission (Korea) Emergency meetings on October 2, 4 and 14; listed 16 affected firms; ordered sector-wide checks and announced reform measures Supervisory response; same-actor question "under detailed investigation" (our translation) Full review of external access points due November 30 and December 31; rule changes and a new act proposed Oct. 2; Oct. 4; Oct. 14; Nov. 5
Financial Supervisory Service and Financial Security Institute On-site investigations from September 30; attacker IPs shared with about 500 firms; FSS identified 28 IPs in 12 countries Investigation; findings reported through press Results not published FSC, Oct. 4; Nocut News; Korea JoongAng Daily
National Police Agency (Korea) Opened a case on October 6 under the Information and Communications Network Act with an initial team of 28; Korean reporting says the team expanded to 43 on October 9 and later added a suspected Electronic Financial Transactions Act violation Criminal investigation; no suspect identified in the public record reviewed Police said they would notify the Serious Crimes Investigation Agency, according to October 20 reporting Tax & Finance News; E-Daily; Newsian (underlying police release not located)
Personal Information Protection Commission (Korea) Attended the October 4 meeting; co-issued the October 6 alert; a PIPC official said whether it investigates Shinhan depends on the FSS findings No incident-specific investigation found in PIPC press releases through November 5 Decision after FSS findings FSC, Oct. 4; iNews24
Ministry of Science and ICT and KISA (Korea) Attended the October 4 meeting; MSIT plans vulnerability checks of about 170 private IT infrastructures, citing recent breaches General response, reported by Yonhap; not specific to this actor Checks due by year end FSC, Oct. 4; Yonhap
Ministry of Foreign Affairs (China) Spokesperson Mao Ning said on October 8 the ministry was not familiar with the case and that China opposes hacking Statement None announced Reuters via The Straits Times

No incident-specific public action was found from US authorities in the sources searched as of November 6, 2026. President Lee Jae Myung called for a thorough investigation, as reported by Kyunghyang and Korea JoongAng Daily; no presidential office text was read. General policy, labeled separately: the FSC's November 5 package and MSIT's inspection plan respond to the whole wave of incidents, not only to this actor.

What remains open

Established in this record

The FSC confirms intrusions and data leaks at named financial firms from September 30 onward; on October 14 it listed 16 firms and about 100,000 leaked records and said whether one actor was behind all 16 is still under detailed investigation. Korean authorities found the same attacker's IP addresses across the first seven firms' incidents. CrowdStrike says recovered files tie an ARTEX instance, Claude Code sessions and several third-party model backends to infrastructure it assessed was likely responsible for the Korean attacks, but its public report does not name the organizations or map sessions to individual thefts. An anonymous Financial Security Institute official separately reported ARTEX traces in Shinhan's logs. Published reporting attributes the early incidents to weaknesses in side systems, including missing or weak authentication, missing device controls, unpatched web flaws, and known vulnerabilities used for malware-assisted log theft. This record is separate from the VAPOR PANDA campaign (IB-2026-016), which CrowdStrike dates from October 17, attributes to a China-linked espionage group, and supports with different indicators; neither CrowdStrike report links the two. (FSC, October 14; CrowdStrike; CrowdStrike, VAPOR PANDA)

Still unknown

How many of the FSC's 16 firms this actor hit is unresolved: Korean authorities linked the first seven through shared attacker IPs and similar methods, Reuters counted at least nine banks targeted or reported, and the FSC says the same-actor question for all 16 is still under investigation. Whether any Anthropic model processed the actor's requests, and how the actor obtained Claude Code, is not stated by CrowdStrike or Anthropic. The October 17 to 28 incidents at Daishin, Mirae Asset and Bithumb have no published link to this actor or to AI; SBS reports 4.4 million scan attempts from North Korean IP ranges since October 21 with no confirmed breach, a separate matter. (Reuters via The Straits Times; SBS)

Next reporting step

Seek the FSS and Financial Security Institute investigation findings on which of the 16 firms share this actor's indicators, any police charge, and a statement from Anthropic on whether its models or accounts were involved. Read the affected firms' own notices, and seek a primary National Police Agency update on the expanded investigation and referral status. No outreach has been sent.

Record updates

  • November 6, 2026: Initial source-checked record published as IB–2026–018. Based on CrowdStrike's report read in full, eight FSC press releases read in Korean, and Korean and international reporting. Firm-level counts rest on firm statements relayed by the press, not on the firms' own notices; the AI-tooling evidence rests mainly on CrowdStrike, with partial corroboration from Hunt.io's infrastructure analysis and one anonymous Korean official; police developments after October 6 rest on Korean press reports; Reuters, NYT, WSJ and SCMP originals and the police website could not be read; no statement from Anthropic, DeepSeek, Zhipu or xAI was found.

How we assess impact

The four-step scale is an editorial assessment of documented impact, not a technical vulnerability score or a probability forecast. Each brief explains its rating; unknown impact is not counted as zero harm.

  1. 1 / LimitedA bounded failure with no demonstrated external impact.
  2. 2 / MaterialDisruption or unintended changes outside the intended task.
  3. 3 / SeriousThird-party compromise or sensitive-data access.
  4. 4 / CriticalDemonstrated widespread or severe harm.

Source counts measure linked documents, not independent corroborations. Case IDs identify this publication’s records.

Read our methodology