Items whose underlying event or first publication falls between 15 and 16 October 2026.
Everything older, and everything already covered in the 14–15 October brief, is listed
with its exclusion reason in section 04.
APAC · South Korea
Escalation
Low–medium confidence
From data theft to attempted loan origination
DB Savings Bank blocked an attempt to take out loans using roughly 100 employee
accounts. The applications were stopped at the credit-inquiry stage and no funds
were disbursed. The report attributes the source to a Chinese IP address.
The significance is the change in objective. The same access that leaked customer
records in this campaign was here pointed at the bank's own lending process, using
staff identities rather than customer ones.
OutcomeAttempted, blocked, no loss reported. Not a successful fraud.
AttributionAn address geolocated to China is a property of the address, not an attribution to a Chinese actor. No actor is named in the reporting.
Source: ChosunBiz and Chosun exclusive, 15–16 Oct 2026 (English, Korean and Japanese editions of one outlet). Single-sourced — no independent confirmation, no number of accounts or disbursement detail visible. Treat as an indicator of direction, not a confirmed loss event.
APAC · South Korea
Confirmed disclosure
Medium confidence
OK Savings Bank confirms 250 customers affected
The bank reported an intrusion to the FSS on 13 October, confirmed the scope on
15 October and began notifying customers the same day. The exposed fields are
names, dates of birth, phone numbers, account numbers, annual income and loan
amounts. Access to the affected system ran for roughly five and a half hours on
11–12 October.
This sits inside the wider Korean wave: sixteen financial firms and approximately
100,000 records, with the crypto exchange Gopax among the named entities. The FSC's
inspection of 555 firms found 130 with shortcomings, chiefly unapplied patches,
ageing systems and thin out-of-hours monitoring.
Regulatory follow-onFSC to tighten CEO and board security accountability, move large firms to twice-yearly vulnerability checks, and stand up AI-based joint threat monitoring.
Record-count tensionThe FSC figure of ~100,000 records and Zscaler's figure of ~67,000 individuals describe the same campaign at different scope. The regulator's number is the one to use; the two are not additive.
Sources: DigitalToday, Seoul Economic Daily, SBS, Korea Times, BleepingComputer (14–16 Oct). Regulator statements via FSC press releases. Independent of the Chosun exclusive above.
APAC · Japan
New IOCs
Medium confidence
JPCERT/CC publishes three addresses and an AI-usage claim
Japan's national CERT published an examination of attack servers behind the
country's breach wave, reporting that attackers used AI to scan for known
vulnerabilities and to attack services through their APIs. Three addresses were
released as indicators. They are enriched independently below.
CorroborationTwo of three carry Shodan's own c2 tag, assigned independently of JPCERT. That is genuine corroboration of role for those two.
Shared configTwo of the three expose an unusual stack — 53, 389, 465, 587, 8083, 8899. Flagged, not used as a selector: the mail and LDAP ports are a common server profile, and I did not validate this combination against a population for precision or recall. It joins nothing.
Scanning behaviourGreyNoise returned "not observed scanning the internet" for all three — a tested negative, not an unknown. Expected for receiving infrastructure: a C2 does not need to scan.
Blocklist checkNot listed in Spamhaus DROP, CINS or Feodo. Tested negative with a passing positive control. Weak evidence: DROP and CINS are network-scope lists unsuited to catching a single VPS, and the Feodo feed is frozen, so a miss there is not a negative.
Report the tension. JPCERT/CC states AI was used but does not show how that
was established; the artifacts it published would look the same if the work had
been done manually. Japanese coverage split on this — Sankei and NICT framed AI
involvement as a possibility, not a finding. Record the claim and the gap.
Sources: JPCERT/CC weekly report 15 Oct; Japan Cyber Watch analysis; Sankei, NCC, TBS. Enrichment is this analyst's own, via no-key sources.
EMEA · United Kingdom
Supervisory
High confidence
Bank of England names AI a systemic risk and asks for bare-metal recovery
Deputy Governor Sarah Breeden, speaking at the Institute of International Finance
annual meeting in Bangkok on 15 October, said AI advances now pose a
“systemic risk” to the global financial system. Her framing was
unusually direct about failure: “It's not enough now to assume that the
cyber attackers won't get through.” She described the worst case as
waking to find a systemically important bank paralysed, and said cyber is
“always the thing that I say keeps me up at night.”
The operative ask is bare-metal recovery — recovery paths standing entirely
independent of a bank's main technology estate, planned end to end across the
financial system rather than institution by institution. The Bank is separately
surveying banks on quantum readiness for encryption risk.
Source: Reuters, via PYMNTS, 15 Oct 2026. Direct quotation. High confidence — an on-the-record statement by a named official at a public venue.
APAC · New Zealand
Supervisory
High confidence
RBNZ and FMA issue joint expectations on frontier-AI cyber risk
The Reserve Bank of New Zealand and the Financial Markets Authority issued a joint
statement on 15 October setting out supervisory expectations for cyber risk arising
from frontier AI. Three risks are named: increased cyber risk, governance and
oversight difficulty, and third-party and concentration risk.
The expectation placed on boards is specific — know where AI is used in the estate,
and know who is accountable for it — alongside a reminder to get the security
basics right before reaching for AI-driven defence.
Sources: RBNZ/FMA joint release; RNZ (16 Oct). Note the FMA page returned HTTP 403 to automated retrieval, so this rests on the release as reported; the primary document was not read directly.
Global
Analytical anchor
High confidence
IMF: in more than 70% of 2026 cases there was no time to patch
The IMF's October Global Financial Stability Report, Resilience, Risk, and
Transformation, finds that in more than 70% of reported cyberattack cases so
far in 2026, software providers had almost no time to patch before exploitation —
against 2021, when close to 300 days was typical. It also records a roughly 40%
shortfall in cybersecurity professionals and flags concentration among a small
number of critical technology providers as a common point of failure.
Released 13 October, so formally outside this window; included because it is the
evidence base the 15 October supervisory statements rest on. The practical reading
for a bank is that patch cadence cannot be the primary control when the patch
window has collapsed to nothing.
Sources: IMF GFSR October 2026 (Chapter 1); IMF blog 12 Oct; Reuters, Computer Weekly, Morningstar. High confidence — primary institutional publication.
AMER · United States
Governance trend
Medium confidence
Processor concentration becomes a liability dispute
A tenth financial institution — Antwerp Exchange Bank of Ohio — joined litigation
against core processor Fiserv, alleging inadequate cybersecurity and specifically
weak multifactor authentication. Fiserv's position is that clients choose their own
security settings. No breach is alleged in the suits.
This is worth leadership attention not as a legal matter but as a governance one:
it is the point at which shared-processor risk stops being an abstract concentration
statistic and becomes a contested question of who holds the evidence and the duty.
Source: American Banker, 15 Oct 2026. Medium confidence — trade press, no court filing read directly.
AMER · United States
Unconfirmed
Qilin lists Telcoe Federal Credit Union
The Qilin ransomware group posted Telcoe Federal Credit Union to its leak site on
15 October. On the same day Incransom listed CoopeCaja, a Costa Rican
savings cooperative.
One source wearing several hats. Every outlet carrying this story — the
ransomware trackers, the briefing sites, the aggregators — is republishing the
same leak-site post. That is one claim, not several, and it is the claimant's own.
There is no victim confirmation, no scope, no independent telemetry, and no
evidence data was actually taken rather than merely asserted. Treat as a lead.
Sources: ransomware.live, Kalir, threatcluster, Today In Cyber, HookPhish — all traceable to the Qilin leak-site listing of 15 Oct.
AMER · United States
Disclosure
Medium confidence
Missouri Central Credit Union breach from a legacy email account
Reported 15 October and filed with Massachusetts regulators on 12 October: a
phishing attack on a legacy email account exposed members' Social Security numbers,
financial account information and credit and debit card numbers. The account
reportedly lacked modern multifactor authentication.
Source: TechNewsReel, 15 Oct 2026; state regulator filing. Medium confidence — the underlying breach notification is a regulatory filing, but this window's reporting of it is secondary.
APAC · India
Low confidence
GhostBat RAT moves onto UPI PINs
Reporting states a RAT has evolved to steal UPI PINs from around sixty
banking, UPI, wallet and fintech applications on Android in India, distributed
through smishing that uses fake traffic-fine notices linking to imitation
mParivahan and Play pages. Payloads are said to be staged in GitHub repositories
to evade scanning, within a wider “GhostX” ecosystem.
Source: Threat Times, 15 Oct 2026. Low confidence — a single low-tier outlet, no vendor research or sample reviewed, no IOCs published. Recorded for vector awareness only; do not build detections on it.
Digital assets
Confirmed exploit
High confidence
UNCX vesting contract drained across four chains
An accounting flaw in UNCX Network's Vesting V2 contracts allowed a small leftover
vesting position to withdraw tokens other users had deposited. Losses reached
roughly $1.49M across Ethereum, BNB Smart Chain, Base and Robinhood Chain, with
BNB Chain accounting for about two-thirds. The root cause, identified by ExVul, is
that release() reduced the global _totalTokenShares
without removing released shares from the calling position's
_depositedShares, so a cancel path double-counted the balance.
Eleven drain transactions were recorded, with copycat wallets and MEV bots joining
once the flaw was public. UNCX froze new vesting positions, raised lock fees, and is
coordinating with law enforcement and SEAL 911.
Sources: Blockaid (loss totals), ExVul (root cause), Crypto Times and Bitcoin.com News, 15 Oct 2026. High confidence on the mechanism — two independent security firms. No funds recovered as of reporting.