>
av.Amit VijayanCYBERSECURITY & RESEARCHLet\u2019s connect
Back to the library

Cyber news

Daily Cyber Threat Brief — November 20, 2026: SBC Medical Group breach hits 1.6 million as n0n leaks Chase, Visa and Mastercard data

Thumbnail for: Daily Cyber Threat Brief — November 20, 2026: SBC Medical Group breach hits 1.6 million as n0n leaks Chase, Visa and Mastercard data

Case file — Lead incident: SBC Medical Group, a clinic management company based in Japan and listed on Nasdaq, disclosed in a filing with the U.S. Securities and Exchange Commission that two cybersecurity incidents exposed customer and employee data. The company discovered the database breach on November 16, 2026, and was notified of the second incident — unauthorised access to administrator accounts on Tribeau, a third-party booking platform — the same day. The database breach exposed basic personal information belonging to 1,624,000 people, including full names, contact details, dates of birth, patient card numbers, member IDs, passwords and survey responses; not every data type was exposed for every person. It also exposed 255,416 reservation requests, 217,769 inquiries submitted to SBC websites, and thousands of treatment description records. Around 20,000 employee account records were also taken, including names, IDs and passwords, and for 459 employees the exposed data also included bank account and tax information. The Tribeau incident affected a service used by 56 clinics, exposing reservation information for 12,641 people and treatment names, dates and fees for 6,804 people who received treatment. SBC said it has not confirmed unauthorised access to electronic medical records or information from its mySBC reservation site, and that as of November 18 it had seen no evidence the exposed data had been misused. The method of intrusion and the full scope remain under investigation, and the company said it could not yet estimate the financial impact. Status: confirmed breach; investigation ongoing.

Incident timeline

DateDevelopment
October 2–4, 2026Attackers hit Wellington IT, an IT supplier to credit unions in Ireland and Northern Ireland, with an automated script making about five million requests to exploit an authorisation flaw; private records are accessed using valid credentials.
November 16, 2026SBC Medical Group discovers unauthorised access to its databases and is notified of the Tribeau booking-platform compromise. The n0n ransomware group lists Visa, Mastercard and JPMorgan Chase on its leak site with a 48-hour countdown. Transport for London discovers its Oyster photocard compromise after customers report account-creation emails sent from TfL's own mail systems.
November 17, 2026Cybernews reports the Visa and JPMorgan Chase listings; Visa confirms the incident involved a third-party service provider in Asia-Pacific and says its own systems were not involved.
November 18, 2026SBC files a Form 8-K with the SEC disclosing both incidents. BleepingComputer reports the credit-union breach affecting about 40 Irish credit unions.
November 19, 2026With the 48-hour deadline passed, n0n publishes the leaked datasets; Cybernews' examination finds about 16,000 JPMorgan Reserve customers, more than 6,000 premium Visa customers and about 2,000 Mastercard entries. BleepingComputer reports the SBC breach and the Transport for London breach. Wellington IT's CEO issues a statement confirming it notified credit-union customers of the incident.

1. SBC Medical Group breach exposes data of 1.6 million people, plus 20,000 employee records

The largest confirmed breach of the day comes from Japan. SBC Medical Group, whose clinics receive seven million patient visits a year, disclosed in an SEC Form 8-K that unauthorised access occurred on November 16, 2026 to certain databases within a website system run by its Japanese subsidiary, SBC Medical Group, Ltd., in connection with its management services in Japan. The company confirmed that an unauthorised third party accessed and extracted customer information. The method of intrusion and the full scope remain under investigation.

The numbers are large and the data is sensitive. The database breach exposed basic personal information belonging to 1,624,000 people — full names, contact details, dates of birth, patient card numbers, member IDs, passwords and survey responses — though not all of those data types were exposed for every person. Alongside that, the attackers took 255,416 reservation requests, 217,769 inquiries submitted to SBC websites, and thousands of treatment description records, image filenames and customer reviews. About 20,000 employee account records were also stolen, including names, IDs and passwords; for a small subset of 459 employees, the data also included bank account and tax information.

The second incident is smaller but still concrete. Tribeau, a third-party booking platform used by 56 clinics, reported unauthorised access to clinic administrator accounts, exposing reservation information for 12,641 people and treatment names, dates and fees for 6,804 people who received treatment. SBC was careful about what it did not find: it said it has not confirmed unauthorised access to electronic medical records or to information from its mySBC reservation site in the database breach, and that as of November 18, when the Form 8-K was submitted, it had seen no evidence of misuse of the exposed data. The company said the investigation remains ongoing and that it could not yet estimate the financial impact.

Investigation notes

What is confirmed: the SEC Form 8-K disclosure; the November 16 discovery date for the database breach and the same-day notification of the Tribeau compromise; the 1,624,000-person figure and the data types listed; the 20,000 employee records and the 459 employees with bank and tax data exposed; the Tribeau figures of 12,641 reservation records and 6,804 treatment records across 56 clinics; and the absence, as of November 18, of confirmed access to electronic medical records or evidence of misuse.

What is not known: how the attackers got in, whether the two incidents are connected, the full scope of what was taken, and whether the exposed data will be misused. No attacker has been named and no ransom demand has been reported.

What to watch: SBC's follow-up filings for a confirmed intrusion method and any revision to the affected-person count, and whether the exposed passwords — which customers may have reused elsewhere — surface in credential-stuffing attempts.

2. n0n leaks data on JPMorgan Chase, Visa and Mastercard customers after hitting their vendors

The ransomware group calling itself n0n made good on its deadline on November 19, publishing datasets it claims belong to customers of JPMorgan Chase, Visa and Mastercard. All three companies say the data came from outside providers, not from their own systems — and the leaked files, examined by Cybernews researchers, tell a consistent story of third-party marketing and loyalty platforms rather than payment infrastructure.

The sequence began on November 16, when n0n listed all three companies on its dark-web leak site and started a 48-hour countdown. On November 19, after the deadline passed, the group published the files. Cybernews found about 16,000 JPMorgan customer email addresses, some with phone numbers and account identifiers, all appearing to belong to holders of the invitation-only Chase Reserve card for high-net-worth clients, plus more than 100 employee email addresses. The Visa dataset covers more than 6,000 premium cardholders and appears to come from a marketing platform for Visa's dining programmes in Asia-Pacific, including names, email addresses, phone numbers and booking details. The Mastercard file holds about 2,000 entries, so jumbled that a Cybernews researcher suggested they may be test data rather than real customer records.

All three companies have confirmed incidents at third-party providers. Visa said the incident originated with a service provider in Asia-Pacific, that its own systems were not involved or impacted, and that there is no indication payment data such as card numbers was affected. JPMorgan Chase said in a statement on November 19 that attackers accessed marketing data held by its vendors, which may include some customer names and email addresses, and that it will contact affected customers directly and offer complimentary credit monitoring. Mastercard confirmed a third-party incident involving a limited set of data. JPMorgan also stressed that the breach is unrelated to the service outage Chase customers experienced earlier in the week, which the bank attributed to a software bug in its own hardware. The vendor at the centre of all three incidents has not been named, and researchers noted the three datasets share file layouts and formatting, suggesting a single shared third party.

n0n is a new crew, first tracked in mid-September 2026, and it has moved fast: last week it claimed travel giant Expedia, alleging it stole billions of traveller records — a claim that, like the financial listings, remains unverified in its scale. The group's emergence as a top-three published ransomware actor within a month of appearing is itself a signal worth watching.

Investigation notes

What is confirmed: the November 16 leak-site listings and 48-hour countdown; the November 19 publication of the datasets; Cybernews' examination finding roughly 16,000 JPMorgan, 6,000-plus Visa and about 2,000 Mastercard records; and all three companies' confirmations that third-party providers were hit, with no card numbers reported exposed and no payment systems affected.

What is not known: which vendor was breached, how the attackers got in, whether the Mastercard entries are genuine customer data, and the true scale of the underlying vendor compromise — the published files are samples of what n0n claims to hold, not a verified inventory.

What to watch: whether the shared vendor is identified, whether n0n publishes more, and phishing waves aimed at the exposed high-net-worth Reserve customers, whose names and email addresses are now in criminal hands.

3. Irish credit unions hit through IT supplier Wellington IT — payee data including IBANs exposed

A reported cyberattack on Wellington IT, a Belfast-based supplier whose services are used by about 50 credit unions — 43 of them in Ireland — has exposed sensitive information belonging to members of about 40 credit unions in Ireland. Ireland's Minister of State Robert Troy confirmed to RTÉ that Wellington IT is the third-party service provider linked to the incident, after the company notified affected organisations of a data breach posing a risk of financial fraud, impersonation and targeted phishing to their members.

According to the Irish Examiner, which saw the notices, Wellington IT told customers that an automated script made five million requests to exploit an authorisation flaw in the company's infrastructure. The attack unfolded between October 2 and 4, 2026, and the attacker accessed private records using valid credentials. At least six credit unions have independently disclosed impact, including Capital Credit Union, Phoenix Credit Union, St. Canice's Credit Union, First South Credit Union, Malahide Credit Union, and Limerick & District Credit Union.

The exposed data is the kind that powers fraud: payee records saved in online banking platforms, including payee names, nicknames members used to save payees, IBANs, BICs, bank account numbers, sort codes, payee addresses and payment reference information. The notices stressed that members' login credentials and funds have not been affected, though some credit unions are still determining exactly what was exposed. Wellington IT has not publicly disclosed a security incident itself, but on November 19 its CEO, Colin Mitchell, told BleepingComputer the company had notified its credit-union customers of a cybersecurity incident potentially involving certain information maintained within its CU Online platform.

Investigation notes

What is confirmed: about 40 Irish credit unions affected; Wellington IT as the supplier, confirmed by the Irish government; the October 2–4 attack window, the five-million-request figure and the authorisation flaw, as described in the notices; the payee-data types exposed; and the CEO's November 19 statement.

What is not known: the full list of affected credit unions, the total number of members affected, and how valid credentials were obtained to access the records.

What to watch: further disclosures from the remaining credit unions, and fraud or phishing attempts using the exposed payee details — IBANs and payment references are exactly what impersonation scams are built from.

4. Transport for London breach exposes 265,000 Oyster photocard users

Transport for London has confirmed that a breach of its Oyster photocard systems exposed the account details of around 265,000 customers. The operator discovered the incident on November 16, 2026, after passengers reported receiving emails asking them to create an account they already had — messages that came directly from TfL's own mail systems as a result of the compromise. TfL immediately took the photocard website offline while it investigated, and has since contained the incident and notified the UK's data protection regulator, the Information Commissioner's Office.

The breach notifications now going out to affected customers list full names, phone numbers, email addresses, home addresses, dates of birth, and security questions and answers as potentially exposed. TfL's current assessment is that passwords, bank and payment card details, journey information, and the names and dates of birth of children with Zip Oyster cards were not compromised. The 265,000 figure is up from an initial estimate of 250,000, and TfL says the investigation is not yet complete, so the number could rise further. Oyster photocards remain valid for travel, and customers who need to renew a card or check journey history can do so through TfL customer services while the website stays offline.

Investigation notes

What is confirmed: the November 16 discovery, the account-creation emails sent from TfL's own systems, the photocard website taken offline, the 265,000 estimate, the data types listed in the breach notifications, the exclusions TfL states, and the ICO notification.

What is not known: how the attackers got into the photocard systems, the final number of affected customers, and whether the exposed security questions and answers will be used in account-takeover attempts elsewhere.

What to watch: the final affected count, any evidence of misuse of the exposed data — TfL says it has seen none so far — and the restoration of the photocard portal.

On the watch list

Yesterday's lead story has not moved: The Gentlemen ransomware group's claim against Nvidia remains unproven, with no sample files published and no confirmation from the company, and its countdown runs to about November 28. Today's threat-hunting article takes on one of this week's confirmed exploited flaws instead — the Synology DSM vulnerability CVE-2024-10441, added to CISA's Known Exploited Vulnerabilities catalog on November 18 — with detection queries for finding exploitation evidence. On the exposure front, Shodan currently shows about 789,000 exposed NetScaler instances and 507,000 exposed FortiGate appliances worldwide.

Sources

Keep exploring.

All articles