TLP:AMBER — organization only Financial Sector Strategic Intelligence

A Platform Taken Down, a Breach Wave Still Spreading, and an AI Story That Should Not Be Over-Read

New and materially updated cyber threats to the financial sector across APAC, EMEA and AMER — covering 27 October 00:00 to 28 October 07:45 (UTC).

Window
27 Oct 00:00 → 28 Oct 07:45 UTC
Regions
APAC · EMEA · AMER
Classification
TLP:AMBER — internal,
named recipients
Method
Open-web collection; no dark-web access; FS-ISAC member bulletins not reviewed
Prior briefs
15, 16 and 19 Oct 2026

Key judgements

Six things leadership should know from the last 24 hours

APAC

A platform taken down, and four disclosures that each need their own date

The region's risk this window was third-party operational. In Japan the compromised asset was a VPS platform that brokers and their customers trade on; in Korea it was internal web and groupware systems at institutions that disclosed separately and on different dates.

Japan — GMO Internet: data published after the ransom was refused

HighIn window

GMO's twelfth report on the Onamae.com Desktop Cloud intrusion, published 27 October 19:10 JST, confirmed that data claimed to be customer information had been posted, and stated the company will permanently refuse the demand — on the reasoning that payment would not guarantee deletion and would fund further crime. It has consulted police, is preparing legal action against parties spreading the data, and warned customers not to visit the leak site because visitor information was reportedly being harvested.

The timeline matters for anyone reading only today's headlines. Unauthorised access was detected on 20 October; the service was shut down on 21 October; the in-window event is the publication confirmation. Up to 26,739 customer servers may be affected. GMO told customers to back up, disconnect from the internet, power down and unplug cables before a threatened noon payload — the payload was never activated on customer machines.

The financial consequences are already visible at the edges. Japan's finance minister said five forex firms using the service — including OANDA Japan, Goldenway Japan and Ava Trade Japan — were affected and reported to the FSA. Customers have described unauthorised FX trades with losses in the low millions of yen. GMO is offering JPY 5,000 plus up to JPY 3 million per published item, and a bounty of up to USD 1 million for information leading to arrests. Authenticity of the leaked data remains unconfirmed by the company.

Sources: GMO Internet — 12th report, 27 Oct · NHK World — data released after ransom ignored, 27 Oct · Asahi Shimbun, 27 Oct · TechCrunch, 27 Oct · BleepingComputer — payload never activated · Kyodo — USD 1M bounty

Korea — Daishin Securities: 38,490 customers, announced today

High

Daishin Securities announced on 28 October that 38,490 customers were affected. Abnormal access was detected on 17 October on a server linked to remote account opening for discretionary investment, and confirmed on 26 October after reviewing more than 60,000 signals. Eight data types were exposed: names, emails, addresses, telecom identifiers, bank names, and encrypted account numbers, Daishin account numbers and mobile numbers. The company states there is no evidence of access to core systems, and its chief executive apologised and pledged compensation under law.

Sources: Asia Business Daily, 28 Oct · Korea JoongAng Daily, 28 Oct

Korea — Bithumb and KB Kookmin: a confirmation and a revision

HighCommon-attacker hypothesis unconfirmed

Bithumb confirmed on 27 October that an unauthorised external party had abnormally accessed its internal mobile groupware system; the scope, including whether member data was involved, was still under analysis at publication. Separately, KB Kookmin Bank revised its affected population from 119 to 2,210 — 460 employees and 1,631 customers — on 27 October. That breach was detected on 30 September after an attack lasting roughly 43 hours and disclosed on 2 October, so the in-window element is the revision, not a new intrusion.

What we are not saying: that these share an attacker. The FSS is reported to be examining common vectors and possible AI use; that is an investigation, not a result. Mirae Asset Life's breach (26 October) and Mirae Asset Global Investments' blocked intrusion attempt sit just outside this window and are recorded as context only.

Sources: SBS News — Bithumb, Mirae Asset, Daishin, 27 Oct · Aju Press — KB Kookmin 2,210, 27 Oct · Yonhap, 28 Oct · SBS — FSS governor on AI-assisted attack, 27 Oct

Japan and Korea — the AI-agent reporting, and the three things it does not say

MediumActor unresolved

TrendAI's analysis, published in English on 27 October (Japanese original 23 October), separates three infrastructures. Case A used CyberStrikeAI, an open-source AI-agent penetration-testing platform, against at least 19 organisations, including at least 16 in Japan, plus Taiwan and Hong Kong — targeting legacy web systems at smaller businesses and local public-sector bodies. Case B used an unnamed LLM to accelerate planning and tool development, scanning at least 6,000 Japanese IP addresses with deep compromise at one or two companies over about 24 days. Case C used custom LLM-written scripts against at least 1,300 WebLogic candidates and at least 35 VPN entry points, including the Yamaha RTX1210 common in Japan.

Three deliberate omissions are as important as the findings. It names no financial institution among the victims. It withholds all IOCs to avoid interfering with investigations. And it states the three are distinct from ARTEX, that whether they share one operator is unresolved, and that Simplified Chinese being the working language in all three "is only a weak clue to location or affiliation and cannot establish either". Earlier ARTEX reporting (20–21 October, outside this window) remains the only current vendor chain that names finance as a target set in the region — approximately 80 Japanese companies targeted, eight breaches disclosed in finance, logistics and e-commerce, with a CrowdStrike-reported link to South Korean financial institutions in September.

No source links ARTEX or CyberStrikeAI to the GMO breach, and GMO has not established one.

Sources: TrendAI — Not only ARTEX, 27 Oct · Nippon.com — ARTEX, 20 Oct · CNA, 20 Oct · WSJ, 20 Oct

EMEA

No named incident in the window — and a supervisory deadline in three days

The European items reachable in this window are regulatory rather than operational. We say so plainly rather than filling the section: an absence in the sources consulted is not an absence of incidents.

ECB — AI-related cyber action plans due 31 October

High

Significant institutions are required to submit concrete AI-related cyber action plans to their Joint Supervisory Teams by 31 October 2026, a requirement reiterated publicly on 20 October. The ESRB's October assessment notes a steep rise in cyber risk since its June warning on frontier-AI-driven systemic risk. For a financial institution, this is a documentation obligation that lands before month end and should be evidenced, not asserted.

Sources: BIS — Elderson speech, 27 Oct

Context — the EBA website incident was a precaution, not a breach

HighOutside window

CERT-EU alerted the EBA to two critical flaws in widely used web software on 21–22 October; the site was taken offline as a precaution, no breach or data compromise was reported, and some consultation deadlines were extended. Recorded because it is being bundled into this week's coverage; it is not part of this window and it is not an incident.

Sources: EBA press release

AMER

Leak-site claims, and a commerce platform that is genuinely being exploited

The region's confirmed exposure this window is supply-chain and merchant-side, not a bank breach. The institution-level items are claims only.

Qilin and Play — three claims, no confirmations

LowUnverified

Qilin listed Hawaii Law Enforcement Federal Credit Union and NuVista Federal Credit Union on 27 October; a third-party infostealer-monitoring service reported credential exposure against the first (two users, 62 credentials), which is an exposure indicator, not evidence of the intrusion route. Play listed Money Concepts Capital, a US wealth-management firm, the same day. None of the three has a victim statement, forensic detail or published sample. We carry them as a watch list.

Sources: QPulse — Hawaii Law Enforcement FCU claim · leak-feed records dated 27 Oct 2026 (ransomware.live index), sector field activity:Financial

Adobe Commerce / Magento — CVE-2026-48356 (PolyShell) added to KEV

HighDeadline 10 Nov

CISA added the unrestricted file-upload flaw to KEV on 27 October (CVSS 9.3, CWE-434), alongside the Brotli decoder flaw, with a 10 November remediation deadline under BOD 26-04. Adobe fixed it in APSB26-73 in July 2026, at the time rated priority 2 with no known exploits. Sansec's "PolyShell" analysis says it has been mass-exploited since at least March 2026 — 471 stores compromised in a single hour on 30 March — and feeds the DeepVeinDrilling skimmer campaign, which plants web shells disguised as images under pub/media/custom_options/quote/ and injects a JavaScript loader into Magento CMS tables.

Why it belongs in a financial brief. The victims are merchants, and the payload is a card skimmer. That creates issuer and acquirer fraud exposure and third-party risk for any bank hosting or acquiring merchant estates. It is not a banking-core vulnerability, and we do not present it as one.

Sources: CISA KEV alert, 27 Oct · The Hacker News — PolyShell / DeepVeinDrilling · 953 infected stores · ZeroHunt analysis

Cross-regional

What outlasts the individual incidents

1 · The perimeter moved to the third party

A VPS platform used by FX brokers, internal web systems at Korean institutions, and merchant commerce estates are all cases where the institution's own edge was not the failing component. The common control gap is dependency assurance — whether a provider can isolate its customers from a platform-level intrusion — not edge defence.

2 · Match the restraint in the AI reporting

The most detailed report of the week withholds IOCs, names no actor, and separates three infrastructures. The defensible sentence for a board is: agent-driven intrusion workflows are being used against Japanese and Korean targets; the operator is unidentified; no source connects them to the GMO breach. Anything stronger is an addition, not a summary.

3 · Ransom economics are being tested in public

GMO's refusal to pay, its compensation schedule and a USD 1 million bounty are the clearest recent precedent for a non-payment posture in a financial-adjacent breach. Boards should expect this case to be cited in the next incident decision, and should rehearse the decision path — legal, communications, regulator, customer restitution — before they need it.

4 · Three KEV entries with customer-facing estate relevance

CVE-2026-48356 (Adobe Commerce, 27 Oct), CVE-2026-111497 (Brotli, 27 Oct) and CVE-2026-109618/109619 (PHP core, 26 Oct) all sit in web and application tiers rather than banking core. The first has a card-data payload; the other two affect the web platforms those tiers run on.

Recommendations

What we would do, and by when

Immediate · 0–7 days

  1. Establish whether any trading, treasury or customer-facing service depends on Onamae Desktop Cloud. If so, treat credentials and sessions on those hosts as compromised, and re-verify customer trade disputes against the 20–27 October window — unauthorised FX trades have been reported by customers.
  2. Inventory Adobe Commerce / Magento 2.4.4–2.4.9 and B2B 1.3.3–1.5.3 on merchant-facing estates, patch to APSB26-73 levels, and hunt the pub/media/custom_options/quote/ web-shell pattern and CMS-table script injections.
  3. Submit the ECB AI-related cyber action plan by 31 October if in scope of the JST request.
  4. Do not action the three US leak-site claims beyond monitoring until a victim or regulator confirms.

Short term · 1–4 weeks

  1. Run a third-party concentration review for retail-FX and trading infrastructure, asking specifically whether the provider can isolate customer environments from a platform-level intrusion.
  2. Add AI-agent traffic characteristics to monitoring — high-velocity sequential enumeration against legacy web systems and VPN appliances — without waiting for attribution.
  3. Rehearse the non-payment decision path using GMO as the worked example.

Strategic · 1–6 months

  1. Move dependency assurance from questionnaire to evidence for any provider holding trading sessions or card data. Each of this window's incidents failed at a supplier, not at the institution's edge.

Date verification

Items that looked new and were not

Every item below circulated in the last 24 hours as if current. Each was checked against the primary document that dates it, and excluded from the window.

Date verification — checked against primary reporting, not the aggregator entry
Item as circulatedApparent dateActual event dateReason for exclusion
FSC — 16 financial companies, ~100,000 customer records 27 Oct 2026 14 Oct 2026 Surfaced alongside the 27–28 Oct Korean coverage; it is the FSC's 14 October release. Context only.
Mirae Asset Life breach 27 Oct 2026 26 Oct 2026 Outside the window by one day; bundled into the same coverage.
Qilin claim — Power Funding (GB) 28 Oct 2026 26 Oct 11:54 UTC Outside the window by roughly 20 hours.
ARTEX — Ierae / CrowdStrike attribution 27 Oct 2026 20–21 Oct 2026 Cited inside 27 Oct GMO coverage; context only, and not linked to Onamae.
EBA website incident 27 Oct 2026 21–22 Oct 2026 Outside the window; precautionary takedown, no breach reported.
Adobe Commerce mass exploitation 27 Oct 2026 since Mar 2026 Only the KEV listing is in-window; the exploitation pattern is months old.

Confidence

Why these judgements are not higher than they are

The Korean wave may not be one campaign

Four institutions, four disclosure dates, four different systems. The FSS is reported to be examining common vectors; until it reports, treating them as one actor's work is an assumption. We keep them separate and say so in each card.

The AI-tooling link to finance rests on one vendor chain

ARTEX naming finance comes from Ierae/GMO Cybersecurity, with CrowdStrike adding the Korean link. That is a single chain, and the tooling has since been closed-sourced. The TrendAI report, which is more detailed, names no financial victim and withholds IOCs.

The US claims are claims

Three leak-site listings, no confirmations, and two of the aggregator pages carrying them are auto-generated. A ransomware group listing a victim is evidence that a group said something, not that an intrusion occurred.

EMEA's silence is a sourcing artefact

FS-ISAC member bulletins were not available to this collection, and no European regulator published an incident notice in the window. The correct statement is "not found in the sources consulted".

Sources

Source register

APAC — Japan

APAC — Korea

APAC — AI tooling

EMEA and AMER

← Back to main page