1.2 million account holders
On February 18, 2026, the French Economy Ministry announced that a hacker had successfully breached the FICOBA (le fichier des comptes bancaires et assimilés) national bank account database. The attacker gained access by using the stolen credentials of a government official. The breach, which took place in late January 2026, resulted in the unauthorized access of data related to 1.2 million bank accounts. The exposed information includes sensitive Personally Identifiable Information (PII) such as full names, addresses, bank account numbers, and, in some instances, tax identification numbers. The ministry has asserted that more critical data like account balances and transaction histories were not accessible, and no funds could be moved. The incident has been reported to CNIL, France's data protection authority, and a criminal investigation is underway.
The attack vector in this incident was the compromise and misuse of legitimate credentials. An unknown threat actor obtained the login credentials of a French government official, which provided them with authorized access to the FICOBA database. This method bypasses perimeter defenses by appearing as legitimate user activity. After gaining access, the attacker was able to view and potentially exfiltrate the records of 1.2 million individuals.
The French government detected the intrusion, blocked the attacker's access, and took steps to prevent data exfiltration. The motivation for the attack is currently unknown and could range from financially motivated crime (gathering data for future fraud) to state-sponsored espionage.
T1078 - Valid Accounts: The core of the attack was the use of a legitimate, stolen government official's account to access the database.T1566 - Phishing or T1110 - Brute Force: The initial compromise of the official's credentials likely occurred through phishing, password spraying, or a similar credential theft technique.T1213 - Data from Information Repositories: The attacker accessed and collected sensitive data stored within the FICOBA database.T1048 - Exfiltration Over Alternative Protocol: While the ministry claims to have prevented exfiltration, the attacker's intent would have been to transfer the collected data out of the government network.This breach carries significant risks for the 1.2 million affected French citizens:
While the inability to move funds is a mitigating factor, the value of the stolen PII on dark web marketplaces remains high, and the long-term risk to victims is substantial.
D3-RAPA - Resource Access Pattern Analysis.D3-MFA - Multi-factor Authentication.Enforcing MFA on access to the FICOBA database would have prevented the attacker from using the stolen credentials.
Mapped D3FEND Techniques:
Strictly controlling and monitoring accounts with access to sensitive national databases.
Mapped D3FEND Techniques:
Continuously auditing access logs for the FICOBA database to detect anomalous activity, such as high-volume queries.
Mapped D3FEND Techniques:
Training government employees to prevent the initial credential compromise via phishing.
The French government must mandate the use of phishing-resistant Multi-Factor Authentication (MFA), such as FIDO2 security keys or smart cards, for all access to the FICOBA database and other sensitive systems. This incident was caused by the theft of a single password. With MFA in place, the stolen credential would have been insufficient for the attacker to gain access. This single control is the most powerful defense against credential-based attacks and would have almost certainly prevented this breach. The implementation should be prioritized for all accounts with privileged access to national databases containing citizen PII.
To detect similar breaches in the future, the French government should deploy a User and Entity Behavior Analytics (UEBA) solution to perform Resource Access Pattern Analysis on the FICOBA database. The system should learn the normal query behavior for each official's account, including the volume of data typically accessed, the time of day, and the source IP/location. An alert should be automatically generated when an account deviates significantly from this baseline, such as by querying 1.2 million records. This provides a critical detection layer that can identify a compromised account being abused, even if the attacker is using valid credentials.
Implement strict thresholding rules on data access within the FICOBA application itself. For example, configure a rule that triggers a high-severity alert and potentially a temporary account lockout if any single user account requests or exports more than a certain number of records (e.g., 1,000) within a short time window (e.g., one hour). This hard-coded limit acts as a safety brake, preventing a runaway query from a compromised account from exfiltrating the entire database. While it might create some friction for legitimate use cases, those can be handled as exceptions. This technique provides a deterministic control to limit the 'blast radius' of a compromised account.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats