Window: approximately 6 November 09:00 SGT to 7 November 09:00 SGT. New and overnight developments, deduplicated against the 6 November edition, with gaps stated plainly.
CVE-2026-19868 — SSLVPN SAML / MFA bypass, exploited in the wild, no public PoC, no workaround. Patch Gen7 / Gen8 firewalls.
CVE-2026-123158 — Previdian confirms root access on an Alpine honeypot; eight attempts, all from one IP, under nine hours after disclosure.
Korean brokerage discloses 3,800 account numbers and 35,255 employee records; Malaysian bank’s site defaced, internal-access claim unconfirmed.
Singapore agencies warn against giving AI agents access to banking, government or healthcare accounts — hidden instructions could trigger transfers.
The Korean wave reaches a major brokerage — and a Malaysian bank’s website is defaced the same night. Mirae Asset Securities said on 7 November that unauthorised access on 4–5 November exposed about 3,800 customer account numbers and personal data of 35,255 current and former employees and contractors; no account-holder names leaked with the account numbers, and no financial loss has been confirmed. Hours earlier, Bank Rakyat’s corporate website was briefly defaced by an actor calling itself “Marlanwg”, claiming internal access and a data sample — the defacement is confirmed, the internal-access claim is not, and the bank has only confirmed an outage. The Mirae Asset disclosure follows the regulator’s 5 November count of 40 incidents at 37 Korean financial firms since 30 September.
Two edge flaws are now confirmed exploited — and one of them is new to CISA’s exploited list. SonicWall’s SonicOS SSLVPN SAML / MFA bypass (CVE-2026-19868, CVSS 7.5) was added to CISA KEV on 6 November with a 20 November federal deadline; it needs valid alternate-method credentials, has no workaround and no public PoC. Separately, OpenSSH’s musl password bypass (CVE-2026-123158) went from “PoC labs exist” to confirmed exploitation within a day: Previdian saw the first attempt under nine hours after disclosure and confirmed root access on an Alpine honeypot — eight attempts, all from one IP. Neither flaw is unauthenticated remote code execution, and the distinction matters for triage.
Chainalysis starts bringing its screening tools back while two Latin American fintechs pause crypto movements. Chainalysis began phased restoration of KYT and address screening on 6 November, with password resets, API-key rotation and IP allowlisting required; Reactor and Data Solutions remain offline. The same day, Nubank and Mercado Pago paused crypto deposits and withdrawals, blaming an external verification provider — neither named the provider, and the link to Chainalysis is an inference, not a confirmed cause. Binance’s Recovery Update #9 reopened more withdrawals, and Binance announced on 6 November that the zero-knowledge proof for its 44-token proof-of-reserves snapshot has been generated — though the public proof-of-reserves page still showed blank verification fields late on 6 November, so live user verification was not yet confirmed.
Group Name | Target Sub-sector / Geography | TTPs (MITRE ATT&CK where available) | Impact
| Group | Target | TTPs | Impact |
|---|---|---|---|
| Unknown actor — Mirae Asset Securities — NEW in this daily edition | Securities brokerage, South Korea | No MITRE mapping published. Unauthorised external access to the mobile-web phone-authentication login service on 4 November and to the internal groupware system (mi-global) on 5 November. The attack method and the attacker’s identity are undisclosed. Access routes were blocked after detection and an emergency response was activated. | Disclosed 7 November (Yonhap, 08:14 SGT). About 3,800 customer account numbers exposed — account numbers only; the company says no account-holder names or other sensitive customer information leaked with them. Personal data of 35,255 current employees, retirees and outsourced staff exposed: names, employee numbers, email addresses, mobile phone numbers and encrypted passwords. Resident registration numbers, passport numbers, driver’s licence numbers and other unique identifiers were not exposed. No malware infection, no service disruption and no financial loss confirmed so far; main systems operating normally. Reported to the Financial Services Commission, the Financial Supervisory Service and the Personal Information Protection Commission; co-CEOs issued a public apology and a temporary customer helpline runs 7 November 10:00–17:00 SGT. Korean press counts this as the fourth Mirae Asset group affiliate to disclose a breach, after the asset manager (28 October) and the life insurer — that count is the press’s, not the company’s. One Korean outlet characterised the attack as a suspected AI-agent attack; that characterisation is the newspaper’s, not in the company’s statement, and is not treated here as confirmed attribution. |
| Marlanwg — Bank Rakyat — NEW in this daily edition (reported / unconfirmed) | Cooperative bank, Malaysia | No MITRE mapping published. Public pages on the bank’s corporate web portal — including personal-financing sections and the iRakyat online-banking login page — were briefly defaced on the evening of 6 November. The defacement notice claimed internal access and a retrieved data sample, and directed bank officials to the encrypted messaging app Session to negotiate data deletion and remediation. The attack method is undisclosed. | Defaced page captured 22:45 SGT on 6 November; pages restored within about an hour, though defaced content was still visible in Google cache at 03:50 SGT on 7 November. At 23:45 SGT the bank said its corporate website was unavailable and directed customers to its iRakyat, BRICK, QR2E and i-bizRAKYAT apps and platforms; it has not confirmed a cyberattack, internal access or any data compromise, and has issued no formal statement on the actor’s claim. Treat the internal-access claim as unconfirmed and the defacement and outage as confirmed. The same actor previously claimed to be offering webshell access to production MySQL databases belonging to the Royal Malaysian Customs Department (per Lowyat — unverified). Context: Bank Negara Malaysia fined Bank Rakyat RM1 million in January 2026 under its Risk Management in Technology framework after a separate earlier cybersecurity incident — not this event. |
| Unknown actor — SMBC Consumer Finance — Update, previously covered | Consumer finance, Japan; customers of 189 partner banks, credit unions and online banks | No MITRE mapping published. No new detail on the attack method in-window. | New fallout in-window (Nikkei, 6 Nov): the guarantee system is suspended and resumption is aimed at mid-November; up to 188 partner institutions have stopped accepting new card-loan applications. Resona Group disclosed 6 November that 5,935 past-customer records were in the leak — Resona Bank 139, Kansai Mirai Bank 5,793, Minato Bank 3 — customers who held card loans in 2002–2019; names, addresses, income, guarantee amounts and email addresses. Resona’s own new-loan intake continues via other guarantors. Ehime Bank disclosed that its customers’ names, addresses, phone numbers, email addresses, driver’s licence numbers and employer information were in the leak; the count is still unknown. All of these are subsets of the up-to-320,118 figure — do not add them to it. The 320,118 (Kyodo / Asahi) versus 321,018 (Nikkei) discrepancy is still unresolved. |
| Unknown actor — Okinawa Bank via contractor LENDY — NEW in this daily edition (separate incident) | Regional bank, Japan — via a debt-collection contractor, not SMBC Consumer Finance | No MITRE mapping published. Unauthorised access on 30 October to the systems of LENDY (Tokyo), a contractor handling debt-collection negotiation records for the bank’s “Chekit” personal-loan product. | Announced 6 November (Nikkei, 18:36 SGT). 211 records possibly leaked: names, email addresses, phone numbers, agent names, repayment amounts and negotiation details. No misuse confirmed yet. This is a separate incident from the SMBC Consumer Finance breach — different contractor, different system — and must not be folded into the SMBC CF total. |
| N0n — Scry Analytics — UNVERIFIED leak-site claim, 6 Nov | US data-analytics and AI services firm holding bank and insurer client data | No MITRE list in the listing reports. Post date is not compromise date; no encryption, exfiltration volume or ransom demand is independently confirmed. | Unconfirmed. The N0n extortion group listed Scry Analytics on its leak site (post discovered 6 Nov, 09:22 SGT — just inside the window), claiming the material includes core banking customer and signer records of a US private-banking client — names, account records, signer roles, addresses and contact details — plus a global insurance group’s party master of 7,904 legal-entity records with relationship structures, and production support-call transcripts and recordings containing consumer names and mobile numbers. The post marks the data “not paid — exposed”. Neither Scry Analytics nor the bank has confirmed it. The private-banking client is not named. Do not treat as a confirmed breach. |
| TraderTraitor — Binance — Update, previously covered | Crypto exchange, global | No new MITRE list in-window. | Recovery Update #9, 6 November (12:00 SGT): withdrawals reopening progressively from 04:00 UTC for 43 assets across 9 networks / 58 combinations (BSC, Base, ETH, Polygon, TRX, SUI), including USDE, PENDLE, ZRO, XRP, FDUSD, SAND and GRT; deposits remain open. Binance targets HYPE, INJ, APT, PLASMA, NEAR and LTC by the end of next week, and all tokens on already-restored networks. No new proof-of-reserves figures in this update. The 44-token proof-of-reserves snapshot (4 November, 00:00 UTC): Binance announced on Friday 6 November that the zero-knowledge proof has been generated (reported via Decrypt and TechFlow), but the public proof-of-reserves page as fetched around 23:00 SGT still showed blank audit-time and verification fields, so live availability for users to verify their balances was not confirmed; no per-token ratios for the 44-token snapshot have been published. The 98% figure is replenishment from company funds, not recovery of stolen crypto. Separately, Reuters (via Korea Herald Business, 6 Nov) reports US Federal Reserve and OCC supervisors began contacting banks to ask whether they had detected unusual activity or service disruptions after the hack; no bank has reported a disruption, and one of the largest US banks contacted Binance’s security personnel directly within hours of the hack. South Korea’s Financial Services Commission held an emergency meeting with crypto exchanges on 6 November to review access controls, wallet-withdrawal approval and administrator privilege management. |
| Unknown actor — Mercado Bitcoin — Update, previously covered | Crypto exchange, Brazil | No MITRE mapping. | No new in-window update. Phased reopening from Monday 9 November stands: view-only access first (balances, statements, holdings), with transfers, withdrawals and trading only in later phases subject to independent security testing — no dates for the later phases. More than $15 million has been frozen with industry help. Loss figures are not reconciled: the company cites about $38 million while researchers (Bitquery about $48.6 million, Chainalysis about $49 million) put it higher; do not quote any as a settled loss. No official technical explanation or entry point has been published. |
| Unknown actor — Crédit Mutuel Arkéa — Update, previously covered | Cooperative banking group, France (incl. online bank Fortuneo and Keytrade Bank in Belgium as subsidiaries) | No MITRE mapping published. Provider-platform route to the bank directly; the bank’s own account used for transfers to other banks, then conversion to cryptocurrency via specialist platforms. | The Paris prosecutor’s cybercrime unit opened an investigation after the bank’s 4 November complaint (reported 6 November). The bank says nearly all operations have resumed, some funds were blocked and recovery efforts continue; it still does not confirm an exact figure — only the order of magnitude (about €100 million). Investigator ZachXBT assesses with “high confidence” that the attack is not Lazarus — his assessment, not a law-enforcement finding. Do not add figures: ZachXBT’s above-$133 million estimate, Bitquery’s $108.8 million in USDC withdrawals (1–2 November) and a later Bitquery figure of $126.04 million to 17 wallets measure different things, and the bank-to-chain link is not publicly proven. The provider is still unnamed, and the attack method, the actor and the recovery amount remain undisclosed. The $133 million figure remains the investigator’s estimate, not a bank-confirmed loss. |
No new in-window item was found for Crafty Falcon, the ARTEX operators, Mirax RAT, Brazil’s FGC, FIN7 / Carbanak, Scattered Spider, RansomHub, Cl0p, or a FI-specific Initial Access Broker. Crafty Falcon, ARTEX and Mirax were 5 November research items with no new development in this window, so they are not carried as rows. Absence of reporting is not evidence of absence of activity.
CVE ID | CVSS Score | Affected Product | Exploitation Status | Relevance to Finance
| CVE | CVSS | Product | Status | Finance relevance |
|---|---|---|---|---|
| CVE-2026-19868 NEW · KEV 6 NOV | 7.5 / 7.1* | SonicWall SonicOS SSLVPN (Gen7 and Gen8 firewalls) | In the Wild (KEV) | Added to CISA KEV 6 November; federal due date 20 November; no public PoC known. A user holding valid credentials for an alternate authentication method can bypass SAML authentication controls on the SSLVPN service, and may also bypass SAML-enforced MFA. Affects SonicOS 7.3.3-7015 and older (Gen7) and 8.2.2-8015 and older (Gen8); fixed in 7.3.4-7013 / 8.2.3-8015. Applies only where SAML is configured for SSLVPN logins. No workaround. SonicWall’s own wording is that it investigated “a report of potential exploitation” — the KEV listing is the stronger exploitation evidence. No actor, victim, scale or IOCs published; known ransomware use listed as Unknown. *NVD 7.5 vs SonicWall 7.1. This is not unauthenticated RCE — valid alternate-method credentials are required. Advisory SNWLID-2026-0014 bundles seven CVEs, including CVE-2026-107154 and CVE-2026-107155 (both 8.8, management-interface flaws allowing unauthenticated unauthorised operations under specific conditions) and CVE-2026-82308 (7.5, SSL-VPN denial of service) — no exploitation confirmed for those three. Canada’s Cyber Centre issued AV26-1133 on 6 November. Edge VPN plus MFA bypass is a direct route into a bank’s network; treat as priority patching before 20 November. |
| CVE-2026-123158 NOW EXPLOITED | 8.1 | OpenSSH sshd on musl Linux (Alpine Linux above all) | In the Wild (honeypot confirmed) | Status change in-window: threat-intelligence firm Previdian reported 6 November that the first exploitation attempt arrived under nine hours after CVE publication, and confirmed successful root access on a honeypot running real Alpine Linux and OpenSSH — eight attempts, all from one Japan-based IP, 89.116.89[.]18, running reconnaissance commands (id, uname, hostname) through non-interactive SSH sessions. No production compromise has been reported. Still not in CISA KEV (Previdian lists it on its own KEV). Password bypass: musl’s crypt() returns “*” as an error for passwords over 256 bytes, and password-less accounts also store “*”, so a 257–1,024-byte password logs in to a password-less account. Public PoC / repro lab: oz9un/sshole (GitHub) — the researcher’s own repo, verified genuine; two further verified repro labs are leonjza/sshhole-lab and predkambrij/sshhole-repro. Previdian warns other GitHub PoCs for this CVE are unverified and could contain malware — do not link or run any other. Fix 10.6p2 or patched Alpine packages, restart sshd; workaround PasswordAuthentication no. Alpine is widespread in containers and cloud images used by fintechs; internet-facing sshd on musl hosts is directly exposed. |
| CVE-2026-88771 NEW · METASPLOIT MODULE 6 NOV | 9.5 / 9.8* | Citrix NetScaler ADC and NetScaler Gateway | In the Wild (KEV) | New in-window: a public Metasploit module (6.5.9, 6 November) packages exploitation. Unauthenticated pre-authentication command injection as root, reached by writing attacker-controlled text into the appliance’s logs (a fabricated pitboss failure message) which the maintenance script ns_monuploadd_err.pl later runs as a shell command — execution can lag the request by up to 24 hours. Exploited in the wild as a zero-day before disclosure; in CISA KEV since 27 September (due date 30 September, passed). Affects all deployments in the default configuration; no optional feature needed. Fixed in 14.1-73.37 and 13.1-64.23. Citrix says patching does not remove existing implants — check for persistence, not just the patch. *CVSS v4.0 9.5 (Citrix) vs v3.1 9.8 (NVD). NetScaler ADC / Gateway is widely used as a finance perimeter and remote-access device. |
| CVE-2026-76443 NEW · METASPLOIT MODULE 6 NOV | 9.8 | Cisco Secure Email Gateway and Secure Email and Web Manager, 15.5 and earlier | In the Wild (KEV, sibling) | New in-window: a public Metasploit module (6.5.9, 6 November). Rapid7 describes the module as an S/MIME / email-parsing SQL injection leading to unauthenticated root RCE via a crafted email, and says it has “reason to believe” the module maps to CVE-2026-76443 — Cisco’s advisory is vague, so treat the CVE mapping as Rapid7’s, not Cisco’s. The actively exploited zero-day in the same advisory family is the sibling CVE-2026-76461 (9.8, email-parsing SQL injection to root RCE, in CISA KEV since 14 September). Apply the fixed builds from Cisco advisory cisco-sa-esa-inj-2bLVGmhX; no workaround exists. Email gateways sit in front of every bank’s mail flow, so an unauthenticated root RCE there is a direct route to mail interception and credential theft. |
| CVE-2026-97229 NEW · METASPLOIT MODULE 6 NOV | 10.0 | GitLab CE / EE | In the Wild (KEV) | New in-window: a public Metasploit module (6.5.9, 6 November). CI/CD RegExp integer-overflow RCE as the git user; authenticated, requiring write access to a public project. In CISA KEV since 29 October. GitLab hosts source code and CI pipelines — including for fintechs that self-host it — so a packaged RCE lowers the barrier for opportunistic attacks on unpatched instances. |
| CVE-2026-119977 Due date passed 6 Nov · NEW development | 8.1 / Low* | WordPress core 4.7.0–7.1.3 | In the Wild (attempts) | Federal due date passed 6 November; the new development is that installing the fix can itself expose a site one last time. Researcher Umut Bayram (Picus Security, via The Hacker News, 6 Nov): the update that installs the fix still unpacks its files using the site’s old, unpatched code, so an attacker who strikes at the right moment during the fix install can run code on the server. Advice: block web access to wp-content/upgrade/ before updating. Wordfence has blocked 240,000+ attempts by 5 November (peaking at 74,000+ on 30 October). Still no victim publicly named and no confirmed compromise tied to this flaw — blocked attempts are not compromises. Public PoC published 4 Nov: lysophavin18/CVE-2026-119977 (GitHub) — research PoC with a lab run. A second repo claiming to bypass the 7.1.4 fix holds no code, only a download link, and is flagged as a likely malware lure — do not download it. *Wordfence 8.1 vs WordPress Low. Fix 7.1.4 / backport. |
| CVE-2026-107441 | 8.8 (Zyxel) / 9.8* | Zyxel GS1900 series switches, ten models, web management interface | In the Wild (zero-day) | No change in-window. The June fix added a check that ran after the unsafe copy in /cgi-bin/dispatcher.cgi, so June-patched firmware stayed exploitable. Payloads observed: Jitterly backdoor and Sixzut rootkit; suspected Chinese-speaking actor Kapibala / Red Heron campaign (attribution via Binarly / Acronis, not independently verified here). *Secondary analysis rates it 9.8. Fix: 22 Oct firmware; change default credentials. |
| CVE-2026-109593 / 109594 | 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 is critical (9.1): unauthenticated information disclosure via internal file reads. 109594 is medium (6.8): high-privilege SQL injection. SonicWall will not patch — migrate to Network Security Manager. |
| CVE-2026-72898 | 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’s alert AL-2026-158. It can give an unauthenticated attacker admin access and database credentials. Safe releases: 58.24, 59.21, 60.17, 61.11, 62.9, 63.5+. BFSI relevance: self-hosted analytics dashboards that hold database credentials are a credential-theft target, not just a reporting tool. |
| CVE-2026-109618 / 109619 (PHP2Shell) | 9.2 | PHP; PAN-OS and other network/security products | In the Wild | No change in-window. CSA 3 Nov: PAN-OS management interfaces exploited, chained with CVE-2026-46300 to root. Keep management interfaces off the internet. |
| CVE-2026-40217 | 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-116606 / 111560 | 9.3 / 8.6 | Barracuda Email Security Gateway and related products | Not known exploited | No change in-window. Chain gives unauthenticated remote root on ESG. Patch and remove admin interfaces from internet reach. |
| CVE-2026-98432 | 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 | 10.0 | Node-RED / Siemens IoT2050 | In the Wild | No change in-window. Port 1880 without adminAuth remains an active target. |
| CVE-2026-111497 | 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, and about a dozen Splunk products also affected. Check the updated Cisco advisory against your own estate rather than the original short product list. |
No new core-banking, SWIFT/payment-gateway or enterprise file-transfer CVE was reported in this window in sources searched. CISA KEV now stands at 1,769 entries (one addition, 6 November). WSO2 CVE-2025-11969 (due 5 November) is no longer carried — no new development in-window; treat internet-facing instances as overdue rather than upcoming.
Chainalysis began restoring access to its Know Your Transaction (KYT) monitoring service and Address Screening products in phases on 6 November (company update 03:30 EST / 16:30 SGT). Customers must first submit trusted IP addresses for an allowlist, then reset passwords and rotate API keys before registering transactions again. Reactor (investigations) and Data Solutions (threat intelligence) remain offline while external security experts harden the systems; no restoration date has been given. This follows the 4 November disclosure that names, usernames, password hashes and live tokens for all Chainalysis users were exposed to a malicious actor. The company says it has no evidence investigation data was accessed or attribution data manipulated — that is the company’s statement and still provisional — and that the incident is unrelated to the Binance theft. BFSI relevance is direct: KYT is the transaction-screening tool banks, insurers and crypto firms use for AML monitoring, and its outage is already disrupting downstream services (see Emerging fraud).
The breach keeps spreading through the partner network rather than ending at the guarantor: up to 188 partner institutions have stopped accepting new card-loan applications while the guarantee system stays suspended, with resumption aimed at mid-November. Resona Group’s 5,935 records (Resona Bank 139, Kansai Mirai 5,793, Minato Bank 3) and Ehime Bank’s still-uncounted records are all subsets of the up-to-320,118 figure — do not add them to it. The control question for any bank that outsources loan guarantees: which of your customers’ data sits in a guarantor’s system, and how would you know it had leaked?
A second Japanese contractor route in the same window, but a different incident: unauthorised access on 30 October to LENDY, a Tokyo contractor handling debt-collection negotiation records for Okinawa Bank’s “Chekit” personal-loan product, possibly exposed 211 records (names, email addresses, phone numbers, agent names, repayment amounts and negotiation details). No misuse has been confirmed yet. The pattern to note is not the size — 211 records is small — it is that customer data held by a small, specialised contractor is reachable and leakable, and that banks keep learning about it from the contractor’s disclosure rather than their own monitoring.
The N0n extortion group claims data from US analytics and AI firm Scry Analytics, alleging it holds core banking customer and signer records of a US private-banking client plus a global insurance group’s party master of 7,904 legal-entity records. Neither Scry Analytics nor the bank has confirmed it, and the client is not named. If genuine, it is a vendor-holding-bank-data case of the kind that matters most to third-party risk teams; until verified, it is a claim only, and peer banks should check what client data sits with their own analytics and AI vendors rather than wait for confirmation.
Nubank suspended crypto deposits and withdrawals in its app on 6 November, blaming a failure at an external transaction-verification provider; buying and selling for reais inside the app continues, and no timeline was given. Mercado Pago posted a similar notice citing an external data supplier. Neither company named the supplier, and neither has linked the outage to Chainalysis — the link is the reporting outlet’s inference (Nubank’s direct-transfer feature runs on Chainalysis screening, per Nubank’s own launch materials). Treat this as a downstream-outage report, not a confirmed Chainalysis consequence — but it is exactly the kind of disruption the Chainalysis outage was expected to cause, and other firms using the same screening provider should check their own crypto flows now rather than after a customer complaint.
Both of today’s named cases create immediate phishing material. Mirae Asset’s leak gives attackers 3,800 customer account numbers plus the names, email addresses and mobile numbers of 35,255 employees and contractors — enough to impersonate the brokerage to customers and to impersonate staff internally. Bank Rakyat’s defaced pages were still visible in Google search results at 03:50 SGT on 7 November, and the actor’s extortion-style message will be copied into phishing within days. Customers should be told to use the official apps and known channels only: Mirae Asset is running a temporary helpline (7 November, 10:00–17:00 SGT), and Bank Rakyat has directed customers to iRakyat, BRICK, QR2E and i-bizRAKYAT.
Arkéa, Binance and Mercado Bitcoin stories remain live phishing and laundering bait, and the SMBC Consumer Finance breach adds a new one: affected customers are to be contacted individually by email or SMS, and SMBC and its partners warn not to click links in such messages and to verify via official sites. Any message citing loan-guarantee details, an email address from the Arara leak, a withdrawal-restoration offer, or the Bank Rakyat incident should be treated as suspect until verified through a known channel. Verify via official status pages only, never via links in messages claiming to restore withdrawals, refunds or loan access.
Techniques actually published for this edition. No mapping is invented where a source published none, and older research recirculated in-window is marked as context, not as a new sighting.
| MITRE technique | Behaviour | Seen in this edition | BFSI relevance / detection |
|---|---|---|---|
| No mapping published | Unauthorised external access to a mobile-web phone-authentication login service and to an internal groupware system; method undisclosed | Mirae Asset Securities — disclosed 7 Nov | Review web login and groupware access controls; watch for phishing and impersonation using the exposed employee contact details and customer account numbers; check whether staff credentials need resetting given the encrypted passwords exposed. No MITRE ID was published for this behaviour in sources read. |
| No mapping published | Website defacement with an extortion-style claim of internal access and a retrieved data sample; bank confirms an outage only | Bank Rakyat — 6 Nov | Treat the internal-access claim as unconfirmed; watch for a formal bank statement and any leaked data sample; warn customers against phishing citing the incident. No MITRE ID was published for this behaviour in sources read. |
| No mapping published | Valid credentials for an alternate authentication method bypass SAML controls — and SAML-enforced MFA — on an SSLVPN service | SonicWall CVE-2026-19868 — KEV addition, 6 Nov | Audit SSLVPN authentication methods for any alternate login path that is not subject to SAML / MFA; patch to 7.3.4-7013 / 8.2.3-8015. No MITRE ID was published for this flaw in sources read. |
| No mapping published | Oversized-password authentication bypass on musl sshd; first attempt under nine hours after disclosure, root on a research honeypot, reconnaissance commands (id, uname, hostname) over non-interactive SSH | OpenSSH CVE-2026-123158 — Previdian, 6 Nov | Hunt sshd logs for “Accepted password” entries for accounts with no password, especially from 89.116.89.18; patch to OpenSSH 10.6p2 and restart sshd, or set PasswordAuthentication no. No MITRE ID was published for this CVE in sources read. |
| No mapping published | Public Metasploit modules weaponise already-known flaws: NetScaler pre-auth log-injection RCE, Cisco Secure Email Gateway unauthenticated root RCE, GitLab authenticated RCE | Rapid7 Metasploit 6.5.9 — 6 Nov | Patch perimeter and mail-gateway devices now — packaged exploitation lowers the barrier for opportunistic attacks on unpatched instances. No MITRE ID was published for these modules in sources read. |
| No mapping published | Loan-guarantee system breach fallout: up to 188 partner institutions halt new card-loan applications; Resona Group 5,935 records; a separate contractor route exposes 211 Okinawa Bank records | SMBC Consumer Finance / LENDY — 6 Nov | Partner-bank notification and phishing watch on leaked licence numbers, income and guarantee amounts; check what customer data sits with guarantors and small specialist contractors. No MITRE ID was published for these behaviours in sources read. |
No technique in this edition was published with a MITRE ID in sources read. Recurring watch (context only, not a new sighting): valid-account / cloud-account abuse (T1078.004) from the LLMjacking coverage remains the pattern to watch for stolen AI and cloud keys, and it is now directly evidenced by the ARTEX secret-hunting activity — but it is not counted as a new 7 November sighting. One Korean outlet characterised the Mirae Asset attack as a suspected AI-agent attack; that is the newspaper’s characterisation, not the company’s, and it is not counted as a confirmed AI technique here.
AI as a target, AI as a weapon or accelerator, and AI as a risk and control problem for BFSI.
Sophos X-Ops (6 November) previews research for a BSides Sydney talk on 7 November: malicious AI-agent “skills” — a SKILL.md description plus helper code, shared via repositories and marketplaces — whose code does more than the description claims, for example a CSV-summariser skill that also reads credentials, contacts external hosts or runs shell commands, with the extra behaviour hidden by obfuscation (string-splitting, character codes, Base64, zero-width or lookalike Unicode). The proposed defence is deterministic deobfuscation first, then a small local language model judging whether the behaviour fits the declared intent. This is defensive research on a synthetic benchmark — no live incident, no in-the-wild malicious skill and no IOCs were named — so it belongs here as a control problem, not as an attack. No new LLMjacking victim or incident was published in this window; the Google / Mandiant LLMJacking research is dated 2–3 November and is carried as standing risk, not a new incident. The Chainalysis breach’s “offensive agentic techniques” description is context from its 30 October / 4 November disclosures, not a new in-window finding.
No new confirmed AI-driven attack campaign against a BFSI victim was found in this window. The one item that needs care: a Korean outlet (Maeil Business) characterised the Mirae Asset Securities attack as a suspected AI-agent attack. That characterisation appears in the newspaper’s reporting, not in the company’s statement as reported by Yonhap, and the company has disclosed no attack method at all — so it is not presented here as confirmed AI attribution. CERT-In’s Crafty Falcon advisory and the Microsoft / Check Point ARTEX research are 4–5 November items with no new development in this window; they remain standing context, not new sightings, and they are not re-labelled as phishing or deepfake campaigns.
CSA Singapore, GovTech and IMDA issued a joint advisory on 6 November on the safe use of personal AI agents (named examples: Dots, Hermes, Muse, Grok Bot, OpenClaw), following Meta’s Muse launch in Singapore. The warning is practical: personal AI agents act autonomously — they can send messages, make purchases and access accounts without a click — and hidden malicious instructions in websites, emails, calendar invitations or documents could trick an agent into transferring money or leaking personal data. Their five precautions: connect only the apps genuinely needed; do not give agents access to banking, government or healthcare accounts; never share passwords, OTPs, Singpass or credit-card details; require approval before consequential actions; and users remain responsible and liable for what their agent does. If money is at risk: use the banking app’s kill switch, lock the cards and call the bank’s official hotline. This is preventive guidance, not an incident report — no incident figures and no named scam campaign — but it is directly relevant to banks’ fraud and customer-education messaging and to AI-governance controls (agent-tool access, invocation monitoring). Standing context: the US OCC’s Bulletin 2026-54 (4 November) examiner framework for banks’ generative and agentic AI use, and Elastic’s finding that attackers execute commands through Claude Code and ChatGPT desktop in confirmed intrusions. Standing controls still apply: key inventory and rotation, endpoint exposure (no unauthenticated Ollama / LiteLLM on the internet), spend and invocation monitoring with revoke-and-rotate, and agent-tool detection.
No newly reported AI-generated phishing, vishing or deepfake campaign against a BFSI victim was found for 6–7 November. That is absence of reporting, not evidence it has stopped. The Mirae Asset, Bank Rakyat, SinoPac, Arkéa and SMFG cases are not re-labelled as AI campaigns — none attributes them to AI tooling, and the single newspaper characterisation of Mirae Asset as a suspected AI-agent attack is unconfirmed.
Bank Rakyat: the actor’s claim of internal access and a retrieved data sample is unconfirmed — no data sample has been independently verified and the bank has issued no formal statement on it; whether customer data or funds are affected, and whether the bank’s wider digital services are fully restored, is unconfirmed. Mirae Asset: the attack method and the attacker’s identity are undisclosed, and whether the exposed account numbers or employee data have been misused has not been reported; the newspaper characterisation of the attack as a suspected AI-agent attack is unconfirmed. Nubank / Mercado Pago: the external provider is unnamed and the link to Chainalysis is an inference, not a confirmed cause. Binance’s 44-token proof-of-reserves zero-knowledge proof: Binance announced on 6 November that it has been generated (reported via Decrypt and TechFlow), but the public proof-of-reserves page still showed blank audit-time and verification fields at about 23:00 SGT, so live user verification was not confirmed, and no per-token ratios for the 44-token snapshot have been published. The Scry Analytics claim (N0n) is a leak-site claim only, and the MAPFRE Brasil and David L Wade & Associates listings remain unverified. Arkéa: final loss figure (bank about €100 million vs investigator above $133 million / about €118 million), which provider’s platform was used, whether that provider was itself breached, and how much has been recovered; ZachXBT’s not-Lazarus assessment is his own, not a law-enforcement finding. SMBC Consumer Finance: the affected-customer figure differs between outlets — 320,118 (Kyodo / Asahi) versus 321,018 (Nikkei) — and the full list of affected partner institutions is still being pinned down. Mercado Bitcoin: loss total disputed (about $38 million company vs about $48.6–49 million researchers) and entry point unpublished. No in-window evidence was found for new FIN7 / Scattered Spider / Carbanak / RansomHub / Cl0p BFSI attacks, FI-specific IAB sales, SWIFT / core-banking / file-transfer CVEs, a new public FS-ISAC alert, or a new AI-scaled phishing, vishing or deepfake campaign. The joint CISA / FBI / HHS / USDA / DOT advisory on industrial refrigeration controllers (5 November) is cross-sector OT, not BFSI, and is not included as an item.