One confirmed incident at a securities depository, two unverified claims against trading and payments technology, and an availability event at an open-banking aggregator. The common thread is that none of it happened at a bank.
The central depository of the Bucharest Stock Exchange group confirmed on 16 October that its "Servicii Online pentru Investitori" portal — the service where retail investors open accounts — had been the target of a cyberattack. A notice to users, quoted by Romanian outlets, lists the exposed fields: full name, address, personal numeric code (CNP), ID-card series and number, email, phone, and IBAN. The depository states the data was viewed but not modified, and that portal passwords were not compromised.
It states that settlement and registry functions ran normally, holdings and settled-transaction data were not accessed, and that the exchange itself found no BVB-owned system connected to or affected. The portal was taken temporarily offline; counter and postal service continued. The DNSC was notified and an external offensive-security firm engaged.
Three things are Unknown and should be stated as such: the number of affected investors (undisclosed), the attack vector, and attribution. One Romanian outlet places the intrusion around 8 October, which would imply an eight-day gap before disclosure; that date is single-sourced and contested.
Sources: Depozitarul Central press release (PDF) · Romania Journal · RO Times · TSN Media
What it means for usCNP plus IBAN plus phone plus proof of share ownership is a high-quality pretext set. The depository itself warned users about calls citing accurate personal details. The defensive question for any retail-facing portal is narrow and testable: is the boundary between "view" and "export" enforced, and can a single authenticated session enumerate other investors' records?
Regulatory point. A Joint ESAs Q&A published on 2 October (EBA Q&A 2026_7779) clarifies that any successful, malicious and unauthorised access to a financial entity's systems must be assessed for criticality regardless of whether the systems support critical or important functions, and regardless of whether access came via an ICT third party. "Settlement was not affected" is a factual statement; it is not by itself a DORA classification decision.
Netherlands — N0n claims FX liquidity provider's FIX credentials
Unverified claim
The N0n ransomware group listed Solid Trading B.V., a Dutch FX liquidity and trading-technology firm, on 18 October, marked "not paid — exposed." The claimed corpus includes live client trading records, a client database with password hashes, credit limits, clearing paths and fee schedules, trade history, bank matching audit records, and — the item that matters — FIX venue session configurations including login credentials for liquidity providers.
Solid Trading has not confirmed the incident. Every published detail traces back to the group's own leak-site post; the four or five outlets carrying it are reprinting one source, not corroborating each other. Treat the data types as the attacker's claim.
Sources — all downstream of one leak-site post: ransomware.live victim entry · ervik.as · QPulse
What it means for usIf accurate, this is a market-integrity exposure rather than a confidentiality one: LP session credentials permit impersonation of the firm toward its counterparties. The check is inexpensive and low-risk whether or not the claim is true — rotate LP credentials, audit FIX session logs for unexpected source addresses, and watch for order flow inconsistent with mandate.
Luxembourg — claimed cross-tenant exposure at a payment orchestrator
Unverified claim
An underground seller claimed on 18 October to hold roughly 627,000 payment records across 26 merchants, allegedly obtained through a cross-tenant authentication-chain weakness in WhenThen, the payment orchestration platform acquired by Mangopay in 2023. The claimed data includes masked card numbers, BINs, expiration dates, personal data, and fraud-decision "rule traces." Asking price was reported as $5,000.
There is no vendor confirmation and no data sample. A forum listing at a low price is weak evidence; it is also the kind of claim that is occasionally true.
Source: UnderCode News, 18 Oct — a single underground-seller claim, no vendor confirmation, no sample.
What it means for usPayment orchestration platforms sit in the critical-ICT third-party perimeter. If we route card traffic through one, the proportionate response is to confirm the vendor's tenant-isolation assurance and its incident-notification commitment against DORA timelines — not to act on the claim.
UK — open-banking aggregation outage, not an attack
Medium — availability
On 18 October, the open-banking aggregator Tink reported major outages on its Barclays connections affecting all users of manual authentication, refresh and payment initiation, and on its Lloyds Banking Group account-information connections covering Lloyds, Halifax, Bank of Scotland and MBNA. The Lloyds event ran roughly seven hours. Both were attributed to bank-side HTTP 500 errors on token and consent endpoints.
Sources: Tink status, Barclays connection · Tink status, Lloyds Banking Group
We record this as an availability event. No evidence indicates a cyberattack and none should be inferred.
What it means for usAggregation concentrates account-information and payment-initiation availability in a single intermediary. A connection-level fault at one aggregator took out the full user population of that connection, with no workaround at the bank's own app. That belongs in the operational-resilience scenario set alongside cloud-provider disruption.