Revolut Confirms Limited Data Exposure After Fraudulent Government Email Request
Revolut has confirmed the exposure of personal documents and transaction histories belonging to a limited number of customers after the company responded to a fraudulent request that appeared to originate from a government body.
The incident was disclosed on 13 September. Revolut, a London-based financial technology company operating as a digital bank without physical branches, serves approximately 70 million clients worldwide. Since March 2026 it has held a full banking licence in the United Kingdom under the supervision of the PRA and the FCA.
The attack did not involve any compromise of Revolut systems. Instead, the perpetrators submitted the request using an unauthorised email account that possessed valid credentials from a government domain, causing the message to appear legitimate to the recipient.
Data handed over included copies of passports and driver’s licences, selfies used for identity verification, full names, dates of birth, occupations, postal addresses, email addresses and telephone numbers. The package also contained bank statements showing IBAN details, complete transaction histories and records of Bitcoin activity.
The combination of verified identity documents, selfies and detailed financial records significantly increases the risk of new account fraud and highly credible social-engineering attacks that reference real transactions.
Revolut confirmed that customer funds remained secure and that its systems were not breached. The company has blocked the unauthorised email source, notified the relevant authorities and contacted all affected customers. No group has claimed responsibility and there is currently no indication that the data has been sold or published.
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.