Dropbox Lenovo ID Integration Flaw Exposes Thousands of Accounts Without Passwords
A flaw in the integration between Dropbox and Lenovo ID allowed attackers to compromise around 5,000 accounts between August 4 and August 21, 2026, without needing the victims' original passwords.
The vulnerability resided in the federated authentication process. Attackers could register a Lenovo ID using an email address already linked to a Dropbox account because the system failed to properly verify ownership of that address. Once registered, they simply selected the Lenovo ID login option on Dropbox. Because Dropbox trusted the identity asserted by the external service, the email was automatically bound to the existing account, creating an authenticated session without any password prompt.
Only accounts that had previously enabled the Lenovo ID integration and did not have two-factor authentication turned on were exposed. In less than one-third of the affected cases, attackers viewed or downloaded files stored in the compromised accounts.
Lenovo characterized the problem as related to a legacy integration that could incorrectly authenticate certain Dropbox accounts. The company confirmed that its own customers were not directly affected and said it continues to investigate the incident.
After detecting the activity, Dropbox immediately terminated all active sessions authenticated through Lenovo ID, removed the existing associations between the two platforms, and modified the login flow to require the Dropbox password before granting access. The company advised affected users to change their Dropbox and associated email passwords, enable two-factor verification, and review active sessions, connected applications, shared links, and recent file activity.
Related articles
New Container, Old Code: Web Shell Persists Three Months in 1C-Bitrix Environment
Two 1C-Bitrix sites shared a web shell named WebShellOrb after an attacker exploited multiple vulnerabilities in a custom appeal application. The initial compromise went undetected because Nginx logs were retained for only one month, leading responders to conclude that no scanning activity remained visible. After agents showed no malicious code, administrators restarted the container without addressing the underlying issues in the shared filesystem and source code. The attacker regained access weeks later by reusing JWT tokens generated with a hardcoded secret and by exploiting SQL injection flaws that allowed password hash extraction. Shared system user accounts and a common filesystem volume enabled the shell to propagate between sites and survive container recreation. The incident highlighted that redeploying containers and rotating passwords failed to eliminate persistence rooted in unpatched code and misconfigured authentication logic.
How to Check If Your Passwords Have Leaked Online Using Have I Been Pwned
The article explains the common ways passwords end up exposed through site breaches, password reuse, or device infostealers. It details how to use the Have I Been Pwned service to check email addresses against known data leaks and the separate Pwned Passwords tool to verify if a password itself has appeared in dumps. Readers learn that absence from the database does not guarantee safety and that results must be interpreted by examining exactly which data fields were exposed. Practical steps include replacing reused passwords starting with email and financial accounts, enabling MFA or passkeys, terminating old sessions, and scanning devices for malware. The guide also recommends adopting a password manager and staying alert to login notifications. Overall it stresses that regular checks combined with unique credentials and multi-factor authentication form the most effective defense against credential stuffing and account takeovers.
Yandex Restores Access to 96% of Yandex Disk Data After Data Center Attacks
Yandex has recovered access to 96 percent of user data stored on Yandex Disk following attacks that damaged its data centers. Files including documents, photographs, and videos are once again available for opening, downloading, and sharing for the majority of users. The company continues to redistribute Disk capacity across independent external sites to improve overall resilience. Basic operations such as uploading, downloading, and synchronization are now functional, yet the web version still imposes restrictions on bulk actions like downloading entire folders or multiple files at once. Users are advised to rely on the desktop client or API for these tasks during the remaining recovery phase. Yandex publishes ongoing updates on the official Yandex 360 service status page and has not provided an exact date for full restoration.
k0t Operators Breach Corporate Firewalls and VPNs Exposing Over 70,000 Credentials
Group-IB and NyxLab detailed a campaign by the operator k0t targeting exposed firewalls and VPN portals. The operation collected more than 70,000 credentials from network devices and LDAP directory extractions across 84 compromised appliances. Initial access relied on CVE-2025-64446 directory traversal in FortiWeb, CVE-2026-0257 authentication bypass in Palo Alto GlobalProtect, and password brute-forcing against FortiGate devices. Attackers then leveraged CVE-2019-6693 to decrypt FortiOS configuration secrets and chained the noPac technique to reach domain administrator privileges. Persistence was achieved through MeshCentral, AdaptixC2, Atera, AnyDesk, and ngrok, while Rclone handled data exfiltration to cloud storage. Victims appeared on the Qilin and The Gentlemen leak sites, suggesting the operators likely act as initial-access brokers rather than direct ransomware affiliates.