Window: approximately 14 November 09:00 SGT to 15 November 09:00 SGT. New and overnight developments, deduplicated against the 14 November edition, with gaps stated plainly.
AXA Direct Japan says about 597,000 MyAXA accounts may have been affected; Monex Securities says up to 1.13 million email addresses and 1,592 identity-document images may have leaked. Both were disclosed on 13 Nov and missed by the 14 November edition.
KOMSCO’s chak app leaked data of 3,083 users, including account numbers and encrypted card numbers; KBIZ’s Yellow Umbrella site may have exposed member data, with the scale still unconfirmed. The FSI special audit starts Monday.
The 198-token zero-knowledge proof is now published — Merkle root shown, BTC 100.05% — and withdrawals reopened on 87 networks, with full reopening aimed by about 22 November.
Catalogue still 1,781 entries (2026.11.13). A claim that two flaws were added on 14 Nov was refuted — both were added on 24 September. The 13 Nov pair are not carried forward: no new development.
Two confirmed Japanese financial breaches that the 14 November edition missed lead today. AXA Direct Japan says unauthorised access to its MyAXA customer portal may have affected about 597,000 accounts — names, addresses, dates of birth, emails and phone numbers — and its roadside-assistance provider was breached separately. Monex Securities says a third-party account-opening system may have exposed up to 1.13 million email addresses and 1,592 identity-verification document images, including driving licences, My Number card fronts and selfies. Both figures are “may have leaked” maxima, not confirmed theft counts — but both are prime phishing and identity-fraud material, and both companies say no account numbers, passwords or card data were in the affected systems.
Korea’s financial-sector incident wave keeps producing disclosures, and the counting is still contested. KOMSCO confirmed a breach of its chak local-currency app affecting 3,083 users, including account numbers and encrypted card numbers. KBIZ said its Yellow Umbrella mutual-aid site may have exposed member data, with the scale still unconfirmed — do not read the 1.92 million membership figure as a victim count. The FSI special audit starts Monday 16 November. A 14 November report of a “second emergency meeting” and a 16-firm count could not be reconciled with the regulator’s 14 October press release carrying the same figures, so it is not treated as a new development.
Binance’s recovery moved forward, while the patching backlog did not. The 198-token zero-knowledge proof is now live — verified by a live read at 00:08 SGT, with the Merkle root published and BTC at 100.05% — and withdrawals reopened on 87 networks, with full reopening aimed by about 22 November. No new CISA KEV additions were made on 14 November; a claim that two were added was refuted, since both were added on 24 September. N-able’s follow-up hotfix is still in validation with no fix as of 14 November, and a public proof of concept now exists for the Fortinet FortiManager 9.8 flaw, though exploitation is not confirmed.
Confirmed, reported and unconfirmed items are labelled as such. No MITRE mapping is shown where the source published none.
Insurer; MyAXA customer portal and outsourced roadside-assistance provider, Japan
Brokerage; third-party online account-opening system, Japan
State-run mint and security printer; mobile local-currency payment platform, South Korea
Small-business mutual-aid scheme (about 1.92 million members), South Korea
Credit-information centre under the State Bank of Vietnam
Government, banks and financial institutions, telecoms and other sectors; South Korea named among target countries
RMM platform used by MSPs serving small banks and financial firms
Crypto exchange, global
Financial-sector security assessment body, South Korea; assessment staff at banks, insurers, securities firms
Financial services and insurance firms, Canada
Surety bail-bond agency, Los Angeles, California
US auto lender and private-equity firm
Digital payments platform and payment gateway, Honduras
No new CISA KEV additions were made on 14 November. The catalogue stands at 1,781 entries (version 2026.11.13). A claim that CVE-2026-5430 (WSO2) and CVE-2026-71362 (Adobe) were added on 14 Nov is wrong — both were added on 24 September 2026. The two 13 November additions (CVE-2026-123039 and CVE-2026-114713) are not carried forward: no new attribution, IOCs or PoC appeared in-window, and a due date alone is not a new development under the standing rule — the Check Point November Jumbo Hotfix remains a live patching action (see Indicators & defensive actions).
| CVE ID | CVSS score | Affected product | Exploitation status (PoC / in the wild) | Relevance to finance |
|---|---|---|---|---|
| CVE-2026-6460 — NEW, catch-up | 8.8 | PostgreSQL 14–18 (flaw dates to 2004) | Public partial PoC — in-the-wild exploitation not reported | Catch-up — patch published 12 Nov, researcher write-up 13 Nov; missed by the 14 November edition. A type-confusion flaw in PostgreSQL core (composite types plus ALTER TYPE between PREPARE and EXECUTE) lets an authenticated database user with object-creation privileges execute arbitrary code as the OS user running the database server. CVSS 8.8. It was one of 52 flaws fixed in the 12 Nov release (32 scored 8.8); the researcher traces the primitive to May 2004 — effectively every PostgreSQL since then. Researcher Mehmet Ince published the crash PoC and address-leak steps on 13 Nov and deliberately withheld the final RCE step, so there is a public partial PoC, not a copy-paste weapon. Full protection also requires rebuilding C-language extensions. PostgreSQL 14 is now end-of-life (14.25 is its last release). Sibling flaw CVE-2026-116322 lets an unauthenticated client trigger a restart of PostgreSQL 18 servers (denial of service). Not in CISA KEV. PostgreSQL underpins many banking and fintech stacks; authenticated RCE as the database OS user is a high-priority patch. |
| Citrix NetScaler November batch — STATUS, CVE records 13 Nov | 9.5 (highest) | NetScaler ADC, NetScaler Gateway, NetScaler Console, Secure Access Client (Windows/Linux) | Not known exploited — no PoC reported | Status — the CVE records for the batch were published 13 Nov; no new development in this window. SecurityWeek counts 28 fixes, nine critical; SecurityOnline said four bulletins fixing 31 CVEs; The Hacker News said 12 flaws. The count is still unresolved between sources — do not pick one. Headline flaws: CVE-2026-107412 (9.5, memory flaw); CVE-2026-120868 (9.3, memory overflow in packet processing, affects all ADC/Gateway deployments); CVE-2026-120869 (9.4, improper authentication in NetScaler Console, unauthenticated bypass of authentication to access restricted resources — adjacent-network, needs Console IP access); CVE-2026-118268 (8.5, Secure Access Client for Windows privilege escalation to SYSTEM) and CVE-2026-118269 (Linux equivalent). Fixes: ADC/Gateway 14.1-73.57 and 13.1-64.39; Console 14.1-74.34. Citrix says it is not aware of any exploits for the announced vulnerabilities. Separately, CitrixBleed 2 (CVE-2025-5777) is still actively exploited — OffSeq honeypots recorded 316,950 exploitation attempts from 19 source IPs in the last 30 days, last seen 13 Nov 21:41 UTC (14 Nov 05:41 SGT), with DragonForce ransomware as the severe outcome in past cases. |
| CVE-2026-119618 — STATUS, PoC verified as crash-only | 9.8 (Red Hat) / no CVSS yet (NVD) | Apache HTTP Server 2.4.55–2.4.70; standalone mod_h2 2.0.8–2.0.42 | Public PoC — in-the-wild exploitation not confirmed | No new development in-window. The third-party research PoC (GitHub googlesky/CVE-2026-119618, created 12 Nov) was verified directly on GitHub in the 14 November edition. It reproduces heap corruption and ASan crashes on 2.4.70 and clean behaviour on 2.4.71, with a containerised lab and ASan/TSan evidence — but it does not demonstrate code execution. Conflict — flag: Red Hat scores the CVE 9.8 and says public research demonstrates a reliable exploit against a default-configured server; Sysdig (13 Nov) and Abijita (12 Nov) both stress there is no public RCE PoC and no confirmed in-the-wild exploitation as of 12–13 Nov, and the CVE is not in CISA KEV. Treat exploitation status as “public PoC now exists; it demonstrates heap corruption, not code execution; in-the-wild exploitation not confirmed”. Nine GitHub repos now carry the CVE name, including two new labs on 13 Nov that were not verified — do not link them. Race condition in mod_http2 assign_headers(). Fixed in httpd 2.4.71; disabling HTTP/2 is a mitigation. |
| 4EverAble2Shell / Agent2Shell — CVE-2026-90436 + VULN-2026-0009 — STATUS, exploitation confirmed by researchers | 9.8 (CVE-2026-90436) | N-able N-central (on-premises servers with Legacy API enabled) | Exploitation claimed — contested (see actors) | Status — no fix as of 14 Nov (SecurityWeek, 13 Nov; N-able update, 13 Nov; HF3 validation status, 14 Nov). 4EverAble2Shell chains Apache Axis CVE-2026-90436 (9.8) with a separate N-central privilege escalation (Previdian VULN-2026-0009, no CVE yet) to unauthenticated root on the server; it requires the Legacy API to be enabled (non-default). Agent2Shell chains 10+ flaws to SYSTEM on managed Windows agents. Huntback counted 21 production N-central servers mining XMRig, 19 of them on the Hotfix 2 build; N-able says it has seen no signs of compromise using the new flaws and has published IOCs but not confirmed the mining count. Follow-up hotfix HF3 was still in validation on 14 Nov; N-able said it would not be available that day and promised an update on the morning of 15 Nov (US Eastern). No fix as of 14 Nov. PoC repo: MSPNightmare/CVEs — N-Central N-Able (GitHub) — genuine researcher disclosure (Sean Bales), with Previdian’s caveat that the public PoC is unverified and may contain malware. RMM used by MSPs serving small banks; a Hotfix-2 bypass with claimed live exploitation is a live patching and hunting priority. Disable the Legacy API; hunt the IOCs in Indicators. |
| CVE-2026-109618 / 109619 (PHP2Shell) — STATUS, Lazarus targeting reported | 9.2 | PHP; PAN-OS and other network/security products; Check Point Security Gateways | In the Wild | New in-window development: Cyperma’s update to its PHP2Shell abuse report (reported via Yonhap, 15 Nov 08:43 SGT) says Lazarus discussed target countries on a closed dark-web channel on 28 Oct, calling IP bands in Korea, Japan, the US, Thailand, Indonesia and India “quite promising”; 30 of 216 exposed servers analysed were in South Korea. The attribution is Cyperma’s — reported, not independently confirmed. Check Point’s detail adds that the TSGA/TSProxy implants are linked to the PhiliKit toolset (which ESET ties to UNC5221), but Check Point says it “cannot assess the operation with high confidence”. GreyNoise telemetry reported in the 13 Nov afternoon deep-research check shows PHP2Shell exploitation continued through 12 Nov. The Check Point campaign detail is unchanged: attackers chained PHP2Shell in the Mobile Access Portal with CVE-2026-123039 to gain root on unpatched gateways, planted the TSGA backdoor, pivoted to a VMware ESXi host and ran a wiper — “a couple of dozen” systems in one region. Both fixes are in the November Jumbo Hotfix. The PHP2Shell fix had been available since 23 Oct — the one-week patch lag is the lesson. Keep management interfaces off the internet; apply the November Jumbo Hotfix. IOCs: 130.94.19[.]204, 130.94.19[.]168; upload_progress_pwn string in PHP session files; process masquerading as CPconfigdaemon; DREAM_ANNEXATION.txt notes. |
| CVE-2026-124194 — STATUS, Patch Tuesday follow-up | 6.5 | Microsoft Outlook (NTLMv2 hash disclosure) | In the Wild (KEV) | No new development in-window. November Patch Tuesday is the largest on record by Qualys’s count — 1,252 CVEs this month (Qualys, 13 Nov). Conflict — flag: Microsoft’s own count differs (1,362 CVEs across 27 updates per other trackers) and Tenable counted 1,093 — a counting-method difference between trackers, not a new item. About 35% of November patches carried a Low reliability rating in Qualys’s assessment as of 11 Nov. Outlook CVE-2026-124194 remains the exploited item in the batch. Microsoft confirmed the Windows 11 update KB5132061 fails to install on some devices that took the October non-security preview KB5127936, and KB5131085 (Windows 10 / Server 2019) is reported to break Exchange — both affect deployment planning. |
| CVE-2026-127063 — carried | 9.3 | DataComm RMM+ extension for ConnectWise ScreenConnect | Not known exploited — no PoC reported | No change in-window. “The third-party RMM+ extension for ConnectWise ScreenConnect uses a static API secret by default.” Caveat: the CVE wording (“static API secret”) differs from Huntress’s account of a blank access key accepted when none was configured — treat as the same extension weakness pending vendor confirmation. This is the extension weakness behind the SCKit worm. Check RMM+ versions 1.0.31/1.0.32 and remove or re-key the extension. |
| CVE-2026-121529 (“Fortinet2Shell”) — carried | Critical (no CVSS figure in sources read) | FortiClientMac 7.4.0–7.4.7; FortiClientWindows 7.4.0–7.4.7 and 7.2.0–7.2.14 | Public exploit — in-the-wild exploitation not reported | No change in-window. Origin-validation flaw, unauthenticated remote code execution on FortiClient endpoints. PSIRT FG-IR-26-194. Not in CISA KEV. FortiClient is the endpoint agent on bank staff machines; an unauthenticated RCE with a public exploit is a patching priority. |
| Able2Shell — seven CVEs — carried | 9.3 (highest) | N-able N-central | PoC public — exploitation of new chains claimed, contested | No change in-window except the 4EverAble2Shell row above. Original Able2Shell (9 Nov): researcher Sean Bales published PoC code for 33 alleged N-central flaws. Hotfix N-central 2026.4 HF2 (build 2026.4.1.26), released 10 Nov, fixes seven CVEs: CVE-2026-125883 (XXE, 9.3), CVE-2026-125878 (OGNL injection), CVE-2026-125879, CVE-2026-125880, CVE-2026-125881 (SSRF), CVE-2026-125882 (RCE via path traversal), CVE-2026-91000. All hosted servers upgraded by 11 Nov 01:04 UTC. The Able2Shell PoC repository (Oracle-Security/CVEs, path “0-Days/N-Central N-Able”, 26 Python PoC scripts) is a genuine researcher disclosure — linkable as the PoC source, with the caveat that N-able has not validated all 33 findings. |
| CVE-2026-123864 — carried | High (no CVSS published) | Node.js 22.x / 24.x / 26.x (HTTPS servers) | Not known exploited — no PoC reported | No change in-window. HTTPS heap-memory disclosure: a zero-length TLS write re-enters the HTTP parser, and the server copies other connections’ heap memory — including TLS private keys and other users’ requests — into a request body. Fixed in 26.13.1 / 24.22.3 / 22.23.5. Node.js published no CVSS scores and lists no workarounds — upgrade only. |
| Node.js batch — six further High — carried | High (no CVSS published) | Node.js 22.x / 24.x / 26.x | Not known exploited — no PoC reported | No change in-window. CVE-2026-123863, CVE-2026-123865, CVE-2026-123866, CVE-2026-123872, CVE-2026-123874, CVE-2026-126051 (HTTP/2 and TLS memory disclosure / DoS / use-after-free). Six Medium and three Low complete the 16-CVE release. Node.js states 16 CVEs; one aggregator lists 17 IDs — report Node.js’s count. |
| CVE-2026-126263 — carried | 9.8 | FortiMail 8.0.0–8.0.1, 7.6.0–7.6.4, 7.4.0–7.4.6 | Not known exploited — no PoC reported | No change in-window. SQL injection (CWE-89): an authenticated attacker can execute unauthorised code/commands via crafted requests. Fixed in 8.0.2 / 7.6.7 / 7.4.7; FortiMail Cloud already remediated. Internally discovered with the Frontier AI model Claude Mythos. |
| CVE-2026-126155 — carried | 9.1 | FortiMail 8.0.0–8.0.1, 7.6.0–7.6.6, 7.4.0–7.4.8, 7.2 all versions | Not known exploited — no PoC reported | No change in-window. Incorrect authorisation (CWE-863): an unauthenticated remote attacker can obtain an authenticated IBE webmail session as any IBE recipient and read or send their encrypted mail. Fixed in 8.0.2 / 7.6.7 / 7.4.9; 7.2 must migrate to a fixed release; FortiMail Cloud remediated 5 Oct. |
| CVE-2026-121653 — carried | 9.8 | Ivanti Endpoint Manager Core, 2024 SU7 and earlier | Not known exploited — no PoC reported | No change in-window. SQL injection in EPM Core allows a remote unauthenticated attacker to achieve remote code execution. Fix: EPM 2024 SU8. Sibling critical: CVE-2026-121683 (9.4, missing authentication in Cloud Services Application 5.0.8 only; fix 5.0.8.1). Ivanti says it is not aware of any customers being exploited, and none of the 13 CVEs in its 10 Nov batch is in CISA KEV. |
| VSA-2026-062 (no CVE ID yet) — carried | — no CVSS assigned | Xen Orchestra / Xen Orchestra Appliance | Actively exploited | No change in-window. Empty-object login token gives Admin privilege; full XCP-ng host takeover as root. Fixed in Xen Orchestra 6.9.1 / 6.10.0. IOCs: 91.211.251.112:8001 and Tor domain ustar3rqxgnskzgnwkgpofgtvxevm6cx3lxdbwt4mndtveqyaohid.onion:3333. |
| SAP November Patch Day — four CVSS 10.0 — carried | 10.0 | SAP NetWeaver AS ABAP / Web Dispatcher / Gateway | Not known exploited | No change in-window. CVE-2026-76964 (ICM memory corruption, unauthenticated RCE — “ICM2SHELL”), CVE-2026-89126 (Web Dispatcher memory corruption, unauthenticated RCE), CVE-2026-89103 (Gateway broken access control), CVE-2026-120017 (SAML2 missing authentication). Patch internet-facing systems first. |
| Fortinet batch — eight criticals — STATUS, public PoC for CVE-2026-126170 | 9.8–9.0 | FortiOS / FortiManager / FortiAnalyzer / FortiSASE | Public PoC — exploitation not confirmed | New in-window development: a public proof of concept for the worst flaw, CVE-2026-126170 (9.8, JSON-RPC API, unauthenticated remote code execution on FortiManager/FortiAnalyzer), has been verified on GitHub (Ghost-Bx1/cve-2026-126170-fortimanager-jsonrpc-rce, created 11 Nov, contains working exploit.py and poc.py — genuine, not a lure); the NVD record was modified 14 Nov. Conflict — flag: PatchCVE states public exploitation activity has been reported, while Fortinet’s advisory says exploitation was not known at publication and cve.now says “public exploit code, no confirmed attacks”; the CVE is not in CISA KEV. Do not present exploitation as confirmed. The JSON-RPC API is disabled by default; the workaround is set rpc-permit none. Fixed in FortiOS 7.2.14/7.4.13/7.6.8/8.0.2 and FortiManager/FortiAnalyzer 7.2.13/7.4.12/7.6.8/8.0.2 — some fixes still “upcoming”; apply the FortiGuard virtual patch, keep OFTP/FGFM ports off the internet. |
| Microsoft November Patch Tuesday — carried | Up to 9.9 | Microsoft enterprise stack (Exchange, SharePoint, SQL Server, AD, LDAP, DNS) | One exploited (Outlook CVE-2026-124194 — see row above) | No change in-window. 1,094 newly released CVEs per Microsoft (Qualys counts 1,252 for the month; Tenable counts 1,093 — counting-method differences, flagged not resolved). Notable criticals, none reported exploited: SharePoint CVE-2026-120002 (9.9); SQL Server CVE-2026-116945 (9.8); Windows Search CVE-2026-116928 (9.8, zero-click); LDAP CVE-2026-119958 (9.8, zero-click, unauthenticated); Windows DNS CVE-2026-88218 (9.8); iSCSI CVE-2026-88234 (9.8); Exchange CVE-2026-118207 (8.8); AD DS CVE-2026-118146 (8.8); Schannel CVE-2026-119952 (8.1). Tenable notes the exploited Outlook CVE was discovered by a researcher using Claude. |
| CVE-2026-88771 — carried | 9.5 / 9.8* | Citrix NetScaler ADC and NetScaler Gateway | In the Wild (KEV) | No change in-window. Public Metasploit module (6.5.9, 6 Nov). Unauthenticated pre-auth command injection as root via attacker-controlled text written to appliance logs, later executed by maintenance script ns_monuploadd_err.pl — execution can lag the request by up to 24 hours. In KEV since 27 Sept. Fixed in 14.1-73.37 and 13.1-64.23. Patching does not remove existing implants. *CVSS v4.0 9.5 (Citrix) vs v3.1 9.8 (NVD). |
| CVE-2026-76443 — carried | 9.8 | Cisco Secure Email Gateway and Secure Email and Web Manager, 15.5 and earlier | In the Wild (KEV, sibling) | No change in-window. Public Metasploit module (6.5.9, 6 Nov). Rapid7 describes the module as an S/MIME/email-parsing SQL injection leading to unauthenticated root RCE — treat the CVE mapping as Rapid7’s, not Cisco’s. The actively exploited zero-day in the same family is sibling CVE-2026-76461 (9.8, in KEV since 14 Sept). |
| CVE-2026-97229 — carried | 10.0 | GitLab CE / EE | In the Wild (KEV) | No change in-window. Public Metasploit module (6.5.9, 6 Nov). CI/CD RegExp integer-overflow RCE as the git user; authenticated, requiring write access to a public project. In KEV since 29 Oct. |
| CVE-2026-119977 — carried | 8.1 / Low* | WordPress core 4.7.0–7.1.3 | In the Wild (attempts) | No change in-window. 240,000+ blocked attempts (peaking at 74,000+ on 30 Oct). Still no victim publicly named and no confirmed compromise. Fix 7.1.4 / backport; block web access to wp-content/upgrade/ before updating. Public PoC: lysophavin18/CVE-2026-119977 (GitHub). A second repo claiming to bypass the 7.1.4 fix holds no code, only a download link — flagged as a likely malware lure, do not download. *Wordfence 8.1 vs WordPress Low. |
| CVE-2026-107441 — carried | 8.8 (Zyxel) / 9.8* | Zyxel GS1900 series switches, ten models, web management interface | In the Wild (zero-day) | No change in-window. June fix added a check that ran after the unsafe copy in /cgi-bin/dispatcher.cgi, so June-patched firmware stayed exploitable. Payloads: Jitterly backdoor and Sixzut rootkit; suspected Chinese-speaking actor Kapibala/Red Heron (attribution via Binarly/Acronis, not independently verified). *Secondary analysis rates it 9.8. Not in KEV as of 7 Nov. Fix: 22 Oct firmware; change default credentials. |
| CVE-2026-109593 / 109594 — carried | 9.1 / 6.8 | SonicWall Global Management System 9.5.2 and earlier (end-of-life) | Not reported exploited in-window | No change in-window. 109593 critical (9.1): unauthenticated information disclosure via internal file reads. 109594 medium (6.8): high-privilege SQL injection. SonicWall will not patch — migrate to Network Security Manager. |
| CVE-2026-72898 — carried | 10.0 | Metabase 58+ (free and paid editions) | In the Wild | No change in-window. CSA Singapore warned 4 Nov that this SQL-injection flaw, fixed 6 Aug and on KEV since 11 Aug, is actively exploited and a PoC is public. Public PoC: 4minx/CVE-2026-72898 (GitHub), referenced in CSA alert AL-2026-158. Safe releases: 58.24, 59.21, 60.17, 61.11, 62.9, 63.5+. |
| CVE-2026-40217 — carried | 8.8 | LiteLLM proxy | In the Wild (LLMjacking) | No change in-window. User-ID rebind to PROXY_ADMIN. Update LiteLLM, lock endpoints off the internet, rotate keys. |
| CVE-2026-98432 — carried | 9.8 | Linux kernel IPv4 TCP, 4.4+ | Research exploit only | No change in-window. Demonstrated exploit needs MPTCP; RHEL fixed kernels require reboot, Ubuntu was still in -proposed on 3 Nov. |
| CVE-2026-58115 — carried | 10.0 | Node-RED / Siemens IoT2050 | In the Wild | No change in-window. Port 1880 without adminAuth remains an active target. Siemens scope revision noted 8 Nov (more SIMATIC IoT2050 models). |
| CVE-2026-111497 — carried | 9.2 | Google Brotli; Cisco and Splunk products (Node2Shell) | In the Wild (KEV) | No change in-window. Scope as of 5 Nov: 19 Cisco products affected, dozens under investigation, about a dozen Splunk products also affected. Same Brotli root cause also affects ClickHouse. KEV federal due date fell 10 November, but per the KEV rule a deadline alone is not a new development. Qualys published detection/verification guidance for PHP2Shell and Node2Shell on 12 Nov (four non-intrusive QIDs, two intrusive verification QIDs) and reports 167 million PHP installations across 10,000+ customers; attackers probed PHP2Shell four days before a patch existed. |
Showing all 29 watchlist rows.
Vendor, SaaS and service-provider exposure affecting financial organisations.
Osaka City confirmed 1,078,713 email addresses leaked from its online administrative system after attackers hit Arara, the email-delivery service used by its contractor TKC — email addresses only, no contents or My Number data. The platform’s 6 Nov third report put the total at 81,329,467 email addresses (deduplicated) across up to about 380 client companies, exfiltrated 28–31 Oct; another source cites about 77 million — the two totals conflict, do not merge them. The same platform was also abused 28–30 Oct to send up to about 7.13 million phishing emails impersonating a credit-card company. Osaka Prefecture separately disclosed ID-document images for 12 food-support applicants.
Critique: the count matters less than the channel — a ready-made phishing list of shareholder and citizen emails plus a proven bank-impersonation sending channel. Do not add the per-company figures together — they are subsets of the same incident.
Both of today’s Japanese breaches ran through a supplier. Monex’s breach was in a third-party account-opening system (the contractor is unnamed and the intrusion method undisclosed), and AXA’s roadside-assistance provider Prestige Core Solution was breached separately (detected 29 Oct; Prestige International separately disclosed up to about 5.5 million records, duplicates included, across its own systems on 6 Nov).
Critique: neither company has named its supplier’s failing, and in both cases the breached system sat outside the firm’s own perimeter — the pattern peers should be checking is which third-party systems hold customer identity data and whether those suppliers are in scope for the firm’s own incident response.
No new SCKit wave was found in this window, and N-able’s follow-up hotfix HF3 is still in validation. Both RMM stories remain supply-chain stories first: a compromised MSP panel reaches straight into customer networks. Firms should ask their providers whether they run ScreenConnect with the RMM+ extension and whether they run N-central with the Legacy API enabled, and hunt for RelayTrap, the TrapWatch task and the N-central IOCs in the Indicators section.
Expedia confirmed on 13 Nov that attackers reached its systems through a compromised third-party data platform (a Qubole vendor key, per Wiz/Sentra); the extortion group’s claim of about 1 billion records — 830 million loyalty records, 58 million traveller profiles, 333 million account/credential records — is unconfirmed by Expedia. Travel, not BFSI — included only as a pattern note: a vendor key was the entry route, the same third-party-credential pattern behind wfx-loot.
An outage that began 12 Nov (Exchange Online) disrupted Outlook, Teams, Copilot and Defender XDR for users across 74 countries — about 130,000 Downdetector Outlook reports at peak — and was mostly restored by about 03:00 SGT on 14 Nov, with email queues still draining. Microsoft states there was no malicious activity and no security breach. The UK’s NCSC warned on 13 Nov to beware scam calls and messages exploiting the outage — and a credential-phishing campaign doing exactly that is now confirmed; see the fraud section.
Critique: the incident is operational, not a threat event — but the fraud risk is real and immediate, and it arrived while the monitoring tools themselves were degraded.
The open database that exposed 125 million+ SMS messages, including Swedbank account details and one-time codes, has no new development in this window. Swedbank has stopped using the provider and opened an investigation; CERT.LV is investigating. No evidence anyone other than researchers read the data; no confirmed account takeovers or financial loss.
Account takeover, mobile banking trojans, infostealers, DDoS extortion and vishing/smishing.
Attackers are impersonating Microsoft 365 service-health notifications to exploit the 12–13 Nov outage (Exchange Online incident EX1550543, a network-capacity failure Microsoft says shows no sign of malicious activity). Messages cite the real incident ID, with subject lines “Outage – [six-character code]” and sender display names of an organisation-specific prefix plus “Outage Notification” or “Service Health”. They falsely claim emails held during the outage will be permanently deleted within 24 hours unless the recipient clicks to restore them. Three sender domains are identified: moments-notice.com, planetmaison.com, newbooker.com. Microsoft characterises the campaign as “consistent with credential phishing” but has not confirmed credential theft or malware delivery; no actor attribution has been published. The UK’s NCSC warned on 13 Nov of scam calls and messages exploiting the outage.
Critique: the timing is the point — the campaign arrived while Defender XDR and Safe Links monitoring were themselves degraded by the outage, so the usual safety nets were thinner than usual. Verify via official status pages only.
YES Bank has denied a report by The Banker, a Financial Times Group publication, alleging the bank suffered a cyber fraud loss of about $3.4 million (Rs 32 crore) involving government-linked accounts in an incident towards the end of October 2026. In a clarification issued on Friday 13 November, the bank called the claims factually incorrect: its banking systems had not been compromised, no government accounts had been affected, and it had suffered no monetary loss linked to the reported incident. It has asked the publication for a retraction. No independent forensic evidence of a breach has been published, and The Banker has not publicly responded to the retraction request in the reporting seen.
Critique: report this as a denial, not a breach — but note the separate, earlier disclosure: SG Finserve said on 3 Nov that it detected 15 unauthorised debits totalling ₹5.10 crore from two accounts at YES Bank’s South Extension II branch. That is a separate disclosure, not evidence for The Banker’s claim, and the two should not be merged.
Chennai cybercrime police arrested seven suspected money mules after cybercriminals used stolen credentials of authorised Block Development Officers to access the Tamil Nadu rural development department’s Single Nodal Account (HDFC Bank, CIT Nagar branch) between 12 and 30 October and move ₹22.3 crore in 46 transactions to 24–25 accounts. The money has not been recovered and the main culprits are still at large; the case was registered on 3 Nov.
Critique: the theft is an October event — the arrests are the in-window development. The method (stolen officer credentials used against a government nodal account) is a credential-theft and account-takeover pattern, not a bank-system breach, and the unrecovered funds show the laundering chain worked.
Monex’s 1.13 million email addresses and AXA’s about 597,000 accounts are now impersonation material — expect phishing citing Monex account opening and AXA MyAXA. KOMSCO warned its chak users of voice-phishing and smishing; KBIZ warned of impersonation and loan fraud using Yellow Umbrella details. Arara’s leaked shareholder emails are live phishing bait, and the same platform was already abused to send about 7.13 million phishing emails impersonating a credit-card company. SBI’s confirmed personal data is impersonation material — expect phishing citing SBI loan and account-opening details. KB Capital’s leaked staff and partner details are business-email-compromise material. The Tesouro Nacional leak (names, CPFs, Pix keys) and Caixa’s leaked CPFs are impersonation material for 7.6 million-plus people. The FSI leak gives attackers real assessment-staff contact details and firm names — expect phishing citing the FSI or the evaluation process. SMBC Nikko’s leaked holdings and account details are impersonation material for shareholders. Mirae Asset’s leak gives attackers 3,800 customer account numbers plus names, emails and mobiles of 35,255 employees. Binance, Mercado Bitcoin, Gopax and Nubank/Mercado Pago outage messages remain live phishing bait, and the Microsoft 365 outage is now confirmed as a phishing lure — verify via official status pages only. Watch for Rs 1 test transactions on compromised accounts.
The FBI/DOJ disruption of the North Korean “FaceStealer” scheme (more than $400m stolen over 18 months via fake video calls; 900+ victim webcam videos seized) was announced 12 Nov and covered in the 13 November edition; the 14 Nov write-ups add no new facts. The FBI notes the scheme still “overwhelmingly” relies on genuine stolen video, with AI-generated deepfakes of crypto executives increasingly used. Targets are crypto/Web3 and open-source developers — no named bank targeted — so this is an AI-as-weapon item, not a bank campaign. The $400m figure covers the whole scheme, not deepfakes alone.
Customer allegations of thefts from Bank of Khartoum accounts via the Bankak mobile banking app remain reported / unconfirmed: more than 50 traders and customers in West Kordofan claim millions of Sudanese pounds were stolen, with individual reported losses of SDG 18–45 million. The bank has still not responded to comment requests, and no technical evidence that the app itself was breached has been published. Treat as an allegation, not a confirmed bank breach.
Techniques actually published for this edition’s actors and key vulnerabilities. No mapping is shown where the source published none.
| MITRE technique ID | Technique / behaviour | Seen in this edition | BFSI relevance / detection note | Status |
|---|---|---|---|---|
| — none published | Credential phishing impersonating Microsoft 365 service-health notifications, citing the real incident ID EX1550543 | Microsoft Threat Intelligence alert, 13 Nov (reported 14 Nov) | Direct: corporate M365 credential phishing timed to degraded Defender XDR / Safe Links monitoring. Detect on “Outage – [six-character code]” subjects and the sender domains moments-notice.com, planetmaison.com, newbooker.com. | No mapping published |
| — none published | PHP2Shell exploitation of Windows PHP servers; targeting discussion on a closed dark-web channel | Cyperma update via Yonhap, 15 Nov 08:43 SGT | Banks and financial institutions named among target sectors; 30 of 216 exposed servers analysed were in South Korea. Attribution is Cyperma’s, reported not confirmed. Hunt the PHP2Shell indicators in the Indicators section; keep management interfaces off the internet. | No mapping published |
| — none published | N-able 4EverAble2Shell / Agent2Shell chains (HF3 still in validation) | N-able status, 14 Nov | RMM used by MSPs serving small banks. The Legacy API remains the gating control; Hotfix 2 does not fix the new chains. No new vendor-published mapping in this window; the secondary-summary IDs (T1190, T1072, T1136, T1552, T1496, T1068) were published on 13 Nov, not in this window, and are not carried forward as a new sighting. | No mapping published |
| — none published | Unauthorised access and data viewing at financial-sector portals and mutual-aid sites (Monex, AXA, KOMSCO, KBIZ) | Company disclosures, 13–14 Nov | No intrusion detail was published for any of the four, so no technique can be mapped; detection rests on the companies’ own notices and the fraud-watch indicators. Two of the four breaches ran through a supplier’s system. | No mapping published |
Recurring-TTP watch: the techniques that keep recurring across editions are exploitation of internet-facing management and edge interfaces (RMM panels, gateways, VPNs), weak or default credentials on exposed services (SQL Server 1433, FortiGate VPNs), abuse of trusted third-party channels (MSP remote-access tools, email-delivery and CI/CD services), and now outage-themed credential phishing timed to degraded defences. No technique was published with a MITRE ID in this window — that gap is stated, not filled.
The three AI roles are kept separate. Vendor forecasts are marked as forecasts.
No new AI-target item was found in this window. The wfx-loot campaign’s harvesting of AI service keys (OpenAI, Anthropic, Cursor, Copilot) has no new development in-window, and Binance’s zero-knowledge proof is a reserves attestation, not an AI-target event. The gap is stated plainly: nothing new was published about LLM or API-key theft, exposed LLM endpoints or LLMjacking in this window.
FaceStealer — status (12 Nov announcement; 14 Nov write-ups add no new facts). The North Korean scheme stole more than $400m in cryptocurrency over 18 months by hijacking messaging accounts, inviting victims to video meetings and playing secretly recorded webcam video of a known contact — or, increasingly, AI-generated deepfakes of well-known crypto executives — while faking an audio fault to get the victim to run a malicious fix. The FBI notes the scheme still “overwhelmingly” relies on genuine stolen video. Targets are crypto/Web3 and open-source developers; no named bank was targeted.
Lazarus / Cyperma PHP2Shell targeting is reported as conventional PHP exploitation — it is not presented as AI-driven, and this brief does not re-label it.
No new AI-scaled phishing, vishing or deepfake campaign against a named bank was found in this window.
The Korean regulator continues to describe the FSI and financial-firm incident wave as AI-assisted; the 16-firm count reported on 14 Nov could not be reconciled with the FSC’s 14 October press release carrying the same figures, so it is not treated as a new development here. CSA Singapore’s Advisory AD-2026-017 (covered in the 14 November edition) says AI is letting attackers find and exploit weaknesses faster. No new AI governance or control development was found in this window.
N-able’s HF3 validation delay is a patching-process note, not an AI item — but it is the same detection-time compression the ARTEX reporting warned about: exploitation moved within hours of a public PoC, while the fix is still in validation.
Notable indicators from this edition, and prioritised steps for SOC and vulnerability-management teams.
Every source is hyperlinked to the original vendor, government or primary reporting; translated items link to the original-language article.