Last updated: September 29, 2026 at 8:42 AM UTC
All 891 Vulnerability 357 Breach 144 Threat 383 Defense 7

Alleged Żabka leak advertises source code, Jira data, and a reused GitLab token

A data-leak forum listing is advertising an alleged dataset from Polish convenience-store chain Żabka for 5,000 euros, claiming roughly 541,000 Jira issues, about 230,000 IT service-desk tickets, and source code from 89 GitLab repositories. The post names real internal systems, including the chain's point-of-sale platform and SAP environment, and more than 20 outside vendors. A reviewer of the sample archive found the counts internally consistent and noted that a single GitLab access token appears across all 89 repository dumps, pointing to reused credentials rather than a code flaw. Żabka has not confirmed the breach, and the seller's account has no trading history.

Check
Treat the claim as unverified, but use it as a prompt to check whether single tokens or credentials in your own environment grant access across many repositories or systems.
Affected
Żabka and its listed vendors if the data is genuine; the pattern, one reused access token unlocking 89 repositories, is the same stolen-credential route behind many recent source-code and project-tracker thefts.
Fix
Scope access tokens narrowly per repository, rotate and expire them regularly, enforce phishing-resistant MFA on developer accounts, and watch for bulk exports from source and project-tracking systems that signal credential abuse.

Amgen says patient health and research data stolen from third-party cloud systems

Biotechnology company Amgen disclosed that attackers stole patient and corporate data from multiple cloud systems run by third-party providers, rather than from its own servers. In a securities filing, Amgen said it detected the intrusion in July, confirmed data was exfiltrated, and determined the incident material based on the volume and sensitivity of affected files. Confirmed stolen data includes proprietary company information and patient protected health information, and the company is still assessing whether intellectual property, research and development data, and further patient records were taken. Operations, product supply, and financial systems were not disrupted. Amgen has not named a provider, entry point, or responsible party.

Check
Organizations relying on third-party cloud providers should confirm what sensitive data those providers hold, how it is protected, and whether breach notification and monitoring obligations are covered in contracts.
Affected
Amgen patients and partners whose protected health information and proprietary data sat in third-party cloud environments; intellectual property and research data may also be affected, deepening the impact beyond ordinary personal information.
Fix
Minimize and segment sensitive data held by vendors, require strong access controls and logging on third-party cloud environments, monitor for bulk exfiltration, and prepare for extortion and phishing after healthcare breaches.

Chipmaker Analog Devices confirms a breach and stolen files, says operations are fine

Analog Devices, a major US semiconductor maker, confirmed in a securities filing that an unauthorized party accessed some internal systems and exfiltrated files in a June intrusion, while saying operations were not affected. The company has not named who was responsible. Days before the filing, an extortion group calling itself ExfilSquad listed Analog Devices on its leak site and claimed to hold about 570,000 customer records with personal information and home addresses, but Analog Devices has not linked the June breach to that group, and the claim is unverified. The filing also noted a second, separate security issue unrelated to the June intrusion.

Check
Organizations that share data with Analog Devices should watch for a notification and monitor for phishing, while treating the extortion group's specific claims as unverified until the company confirms details.
Affected
Analog Devices and parties whose data sat in its systems; the company confirms files were stolen in June, while an extortion group's claim of 570,000 customer records with home addresses remains unverified.
Fix
Affected parties should watch for official notice and be alert to targeted phishing. Organizations should segment sensitive data, limit what vendors can reach, and prepare for extortion-driven leaks and unverified claims.

No-logs VPN breach exposes 58 million connection logs it promised not to keep

A breach at SplitVPN, a service formerly called NotVPN that marketed itself as keeping no logs, exposed a 17GB database containing roughly 58 million connection logs. The logs record which device connected to which server and when, running continuously up to the day of the breach, directly contradicting the no-logs promise. Cross-referenced with user and device tables holding emails, last-seen IP addresses, and hardware identifiers, they can reconstruct who connected from where and when for tens of millions of people. The data also includes about 23 million user records and 2.6 million payment records with masked card details. Operator account hashes were exposed too.

Check
SplitVPN or NotVPN users should assume their connection history and account details are exposed, change reused passwords, and watch for phishing and extortion referencing their VPN use.
Affected
Tens of millions of SplitVPN users whose connection logs, emails, IP addresses, device identifiers, and masked payment details were exposed, despite the service's advertised no-logs policy, enabling activity reconstruction and targeted fraud.
Fix
Treat no-logs claims as unverifiable marketing rather than a guarantee, prefer providers with independent audits or verifiable architectures, and where anonymity matters, avoid a single centralized intermediary that decides what to log.

DentaQuest notifies more than 23 million people after a data theft attack

Dental benefits administrator DentaQuest, part of Sun Life, is notifying more than 23 million people that their personal and health information was stolen in a May 2026 network intrusion. The company found unauthorized access on May 20 and determined attackers were in its network between May 17 and 20. Exposed data includes names, addresses, Social Security numbers, member, Medicaid, and Medicare identifiers, and dental and vision health details such as diagnoses, treatments, and billing. The extortion group ShinyHunters claimed responsibility and leaked roughly 234GB. DentaQuest has confirmed at least 15 million affected, with independent analysis putting the figure above 23 million, and is offering two years of monitoring.

Check
People with DentaQuest or associated Medicaid or Medicare dental coverage should watch for a notification, enroll in the offered monitoring, consider a credit freeze, and be alert to health-themed phishing.
Affected
More than 23 million DentaQuest members whose names, Social Security numbers, government program identifiers, and dental and vision health records were exposed and leaked, supporting identity theft and targeted fraud.
Fix
Affected people should freeze credit and monitor benefits statements. Organizations holding health data should segment it, enforce phishing-resistant MFA, monitor for bulk data access, and prepare for extortion-driven leaks.

Vatican prayer app left personal data of 700,000 users exposed

Researchers found that an official Vatican prayer app exposed the personal information of more than 700,000 users worldwide through an insecure configuration. The exposed data included details that can identify individuals and tie them to their use of the app. Faith and health apps are sensitive because the mere fact of using them can be revealing, and religious affiliation is a protected category in many jurisdictions, so even a modest data set carries outsized risk for the people in it. The exposure stemmed from the way the app's backend was set up rather than a sophisticated intrusion, a recurring pattern in mobile app data leaks where access controls are misconfigured.

Check
App developers should review backend access controls and confirm that user data stores require authentication and are not readable by anyone who can reach the endpoint.
Affected
More than 700,000 users of the Vatican prayer app whose personal information was exposed; because the data links people to a religious app, it is sensitive even where individual fields seem limited.
Fix
Developers should enforce authentication on all data endpoints, apply least privilege to backend stores, test for misconfiguration before release, and minimize the personal data collected by faith and health apps.

Chick-fil-A says attackers hijacked loyalty accounts using passwords stolen elsewhere

Chick-fil-A has disclosed a data breach following credential stuffing attacks against customer loyalty accounts. In this kind of attack there is no flaw in the targeted company's systems: attackers take username and password pairs harvested from unrelated breaches and replay them automatically against a login page, and any customer who reused a password elsewhere has their account opened. Loyalty and rewards accounts are attractive because they often hold stored balances, order history, and partial payment details, and they tend to receive less scrutiny than banking logins. Affected customers are advised to change their password.

Check
Chick-fil-A customers should change their account password immediately and change it anywhere else the same password was used, then enable multi-factor authentication where the service offers it.
Affected
Customers who reused a password from another breached service on their Chick-fil-A account; attackers replay stolen credential pairs automatically, and reuse alone is enough for an account takeover.
Fix
Use a unique password per service and a password manager. Organizations should rate limit and monitor login attempts, watch for credential stuffing patterns, and offer multi-factor authentication on consumer accounts.

Suno breach exposes 55 million accounts eight months after a developer was compromised

Data from a November 2025 breach at AI music platform Suno surfaced publicly in July, with Have I Been Pwned indexing 55,282,226 unique email addresses. Alongside the addresses, the corpus held names, phone numbers, physical addresses, and purchase records, plus tens of thousands of Stripe entries containing partial card data: card type, expiry date, and the last four digits. Reporting indicates the intrusion started with malware delivered through third-party code on a developer's machine, which yielded credentials for private repositories and internal databases. Suno has said no sensitive personal information was compromised and has not notified affected users.

Check
Suno users should check Have I Been Pwned, change the password there and anywhere it was reused, and be alert to phishing that references their account or past purchases.
Affected
Roughly 55 million Suno users whose email addresses, names, phone numbers, physical addresses, and purchase records were exposed, with partial card data for a subset; most have not been notified.
Fix
Use unique passwords and enable multi-factor authentication where offered. Organizations should treat developer workstations as high value targets, since third-party code running there can hand over repository and database access.

Estée Lauder says attackers took personal data from its Oracle HR system

Estée Lauder is notifying people that personal information was stolen after attackers reached the Oracle E-Business Suite environment it uses for human resources. The company says an unauthorized third party gained access on or around August 9, 2025, and that it confirmed on June 19, 2026 that personal information had been taken, a gap of more than ten months between intrusion and confirmation. The notice does not name the vulnerability exploited, though the timing lines up with the mass exploitation campaign against Oracle E-Business Suite that ran through last year. Affected people are being offered two years of identity monitoring.

Check
Organizations running Oracle E-Business Suite should confirm the environment is patched against last year's exploited flaws and review access logs from that period, since intrusions there went undetected for months.
Affected
People whose personal information sat in Estée Lauder's Oracle E-Business Suite human resources environment; the data was taken in 2025 and only confirmed in June 2026, leaving a long window for misuse.
Fix
Affected people should enroll in the offered monitoring and consider a credit freeze. Organizations should patch and segment enterprise resource platforms, limit the personal data they hold, and monitor for unusual access.

Hugging Face says an autonomous AI agent breached its production systems

Hugging Face, the largest public repository of AI models and datasets, disclosed an intrusion into its production infrastructure that it says was driven end to end by an autonomous AI agent system. The attacker used code execution paths in the dataset processing pipeline for initial access, then harvested credentials and reached internal clusters, though the company found no evidence that public models or datasets were tampered with. The campaign ran thousands of actions across short lived sandboxes, with self migrating command and control staged on public services. Hugging Face's own AI assisted anomaly detection flagged it, and it has rotated affected credentials and rebuilt compromised nodes.

Check
Users of Hugging Face should rotate access tokens and review recent account activity, and teams should check what credentials their model and dataset pipelines hold and how far those reach.
Affected
Organizations running AI model and dataset pipelines that execute untrusted content; Hugging Face's own dataset processing paths gave an autonomous agent initial access, credentials, and reach into internal clusters.
Fix
Rotate Hugging Face tokens, treat datasets and models as untrusted code rather than data, sandbox processing pipelines, limit credentials reachable from them, and tighten admission controls on clusters running that work.