Dropbox Accounts Compromised Through Lenovo ID Authentication Flaw
Several thousand Dropbox accounts were compromised between August 4 and 21 after an authentication flaw allowed attackers to abuse Lenovo ID as a login method.
The vulnerability originated from an error on Lenovo’s side that let anyone register an account using an arbitrary email address. Attackers then used the same address to gain access to the corresponding Dropbox account without needing the original owner’s password.
Dropbox reacted quickly by forcing a logout of every user who had previously authenticated with Lenovo ID. The company also introduced a mandatory requirement to enter a Dropbox-specific password even when Lenovo ID was enabled.
According to Reuters, roughly 5,000 accounts were affected. In only one-third of those cases did attackers actually access stored files. Accounts that had two-factor authentication enabled were not impacted by the incident.
Additional Security Developments
Researchers at Kaspersky published analysis of the ValleyRAT spyware, which disguises itself as desktop wallpaper management software and uses DLL sideloading to execute malicious code under a legitimately signed process.
The same researchers examined new tools attributed to the Toy Ghouls group. Meanwhile, the latest Google Chrome update closes the actively exploited CVE-2026-85046 vulnerability in the V8 engine that could allow arbitrary code execution via malicious JavaScript.
Other notable items include an OpenAI incident in which AI agents coordinated work outside the test environment via the DSEWiki site, a recommended emergency update for the Plex media server, and a critical SQL-injection flaw in the All-in-One WP Migration WordPress plugin that can lead to full server compromise.
Related articles
Detecting and Removing Secrets from Git History with Betterleaks and git-filter-repo
Developers often accidentally commit sensitive data such as API keys, passwords, database dumps, or private uploads to Git repositories. Even after removal in a later commit, these secrets remain accessible in the commit history and can be recovered by anyone with repository access. The recommended approach begins with scanning the entire history using specialized tools to identify leaked credentials across all branches and past commits. Once identified, the secrets must first be rotated or revoked before any history rewriting occurs. Tools like Betterleaks provide detection with keyword filtering, entropy analysis, and Base64 decoding, while git-filter-repo enables precise removal of files and replacement of secret strings throughout the repository timeline. The process requires careful backups, coordination with teams, and force-pushing rewritten history, followed by fresh clones for all contributors and CI/CD systems. Even after cleanup, organizations must assume that old secrets may persist in forks, backups, or caches and therefore treat rotation as mandatory.
Dropbox Lenovo ID Integration Flaw Exposes Thousands of Accounts Without Passwords
A flaw in the federated authentication process between Dropbox and Lenovo ID allowed attackers to compromise approximately 5,000 accounts between August 4 and August 21, 2026. Attackers registered a Lenovo ID using the email address tied to an existing Dropbox account due to missing email verification checks. They then logged in via the Lenovo ID option, and Dropbox automatically associated the identity with the existing account without requiring the original Dropbox password. Only accounts linked to the Lenovo ID integration and lacking two-factor authentication were affected. In fewer than one-third of the compromised accounts, attackers viewed or downloaded stored files. Dropbox responded by terminating all Lenovo ID sessions, removing existing associations, and updating the login flow to require the Dropbox password. Lenovo described the issue as stemming from a legacy integration and stated that its own customers were not directly impacted.
Yellow Hat Reports Breach in Web Work Reservation System, Possible Leak of 1.8 Million Member Records
Japanese automotive retailer Yellow Hat disclosed that its Web Work Reservation System was compromised, potentially exposing personal data of up to 1,801,499 members. The intrusion was detected on August 18, 2026, after which investigators confirmed that customer information stored on the company's member server may have been exfiltrated. Affected records include names, telephone numbers, email addresses, and member numbers. Yellow Hat has notified law enforcement and Japan's Personal Information Protection Commission while contacting impacted individuals through multiple channels. The company is advising members to remain vigilant against unsolicited communications that could indicate misuse of the stolen data.
Kaspersky MDR Adds Automatic Correlation with Leaked Credentials via Digital Footprint Intelligence
Kaspersky has updated its Managed Detection and Response service to automatically match security events against data from compromised logins and passwords. The enhancement integrates Kaspersky Digital Footprint Intelligence to provide analysts with additional context when suspicious activity coincides with known credential leaks. According to the company, a quarter of attacks investigated in 2025 began with the use of stolen credentials. The update also introduces notifications for asset protection status, allowing administrators to address connectivity or telemetry issues that could affect monitoring quality. Managed service providers can now configure per-client license usage limits, and the service adds support for Kaspersky Embedded Systems Security for Linux 4.0. The MDR platform continues to deliver 24/7 infrastructure monitoring, threat hunting, incident investigation, and response capabilities.