France’s Government Messaging App Tchap Got Breached


France’s Government Messaging App Tchap Got Breached

Pierluigi Paganini
June 10, 2026

France’s government chat app Tchap was breached after a single account was compromised, exposing messages and data from public channels.

Tchap, the encrypted messaging platform developed by the French government for its civil servants and made mandatory last year, was breached on June 7. ANSSI, France’s cybersecurity agency, detected the intrusion. The vector was straightforward: someone compromised a user account and used it to access the platform. No sophisticated technical exploit, just a stolen account.

The attacker claimed responsibility over the weekend before the French Digital Affairs Directorate (DINUM) made any official announcement. They said they got in through a social engineering attack targeting the education shard, specifically matrix.agent.education.tchap.gouv.fr. Their own description of what they found is the more alarming part: they claim to have scraped nearly 650,000 messages, information on over 73,000 accounts, including email addresses and device metadata, and over 13.5GB of documents and media files.

Tchap hack
Source: Frenchbreaches.com

They also allege they found hardcoded LDAP credentials leaked via a PowerShell script shared by a regional director of the French tax authority.

“I social engineered a valid account on the education shard (matrix.agent.education.tchap.gouv.fr). Everything below is what that one account could reach, other shards will have more,” reads the announcement made by the attackers.

DINUM’s official statement attempted to downplay the incident and moved to limit the apparent damage. The agency noted that private conversations are end-to-end encrypted, and that even with a compromised account, historical private messages remain inaccessible.

“At this stage, the account originating the malicious requests has been identified. It was immediately blocked to remove the attacker’s persistent access and allow for a thorough analysis of the data they were able to access.” reads the annuncement. “The potentially exposed user account data includes, at a minimum: first and last name, email address, affiliated entity, and avatar.”

In other words, government experts found the account, blocked it, and are now going through the logs to figure out what was actually reached.

What was reachable through that one compromised account is the operative question. Tchap distinguishes between public chat rooms, open to any user and unencrypted by design, and private rooms, which are encrypted. The attacker’s access was theoretically limited to public room content. But with 300,000 monthly users, many of whom are civil servants who may not have read the fine print on what public means in this context, the contents of those public rooms could still be sensitive.

DINUM notified France’s data protection authority, the CNIL, of the potential exposure of personal data. It also sent a reminder to all Tchap users about how public rooms work.

” In accordance with Tchap’s terms of service, no personal, sensitive, or confidential information should be exchanged in public chats; these exchanges must be reserved for private conversations.” states DINUM. “Tchap remains a secure platform for professional exchanges, provided that each user adheres to the terms of service. No personal, sensitive, or confidential information should be exchanged in public chats; these exchanges must be reserved for private conversations.”

Reminding users after a breach that they weren’t supposed to share sensitive information in public rooms is the digital equivalent of putting up a sign after the accident.

The timing adds context. Prime Minister François Bayrou mandated Tchap for all civil servants and banned foreign apps for work communications in August 2025. For this reason,Tchap is a significantly more attractive target than it was when it launched in 2018 as an internal tool for a limited number of individuals.

Mandatory adoption at scale, without proportional investment in the security review of every architectural decision made years earlier, is a pattern that tends to produce exactly this kind of incident. The investigation is ongoing.

Follow me on Twitter: @securityaffairs and Facebook and Mastodon

Pierluigi Paganini

(SecurityAffairs – hacking, newsletter)







Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


TL;DR

Meta stripped NameTag facial recognition code from its AI app one day after WIRED exposed it on 50 million phones. Meta says no decision has been made.

Meta removed nearly all traces of an unreleased facial recognition system from its smart glasses companion app on Friday, one day after WIRED reported that the software had been quietly embedded in an app installed on more than 50 million phones. The feature, which Meta internally called NameTag, was designed to convert faces captured by the company’s Ray-Ban smart glasses into unique biometric signatures and compare them against a database stored on the user’s device. WIRED also found that faces the system failed to recognise were cropped, indexed, and stored locally for future processing.

Andy Stone, Meta’s vice president of communications, told WIRED on Monday that the feature is “purely exploratory,” adding that no final decision has been made on what to do with it. That characterisation sits uneasily with the evidence WIRED documented. The version of Meta AI published the day of WIRED’s Thursday report contained several code libraries explicitly named for face recognition, a process for running the NameTag recognition pipeline, and a “Person recognised” alert the app would have shown if someone were identified.

Friday’s release stripped all of it out, along with a folder where the app would have stored the cropped images and biometric signatures of unrecognised faces. Meta did not answer WIRED’s questions about why the code was removed or whether the changes were planned before the story was published. A few fragments remain in the latest version, including an internal debug menu label and a dormant link meant to open a recognised person’s profile, pointing to parts of the system that are no longer there.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

The gap between Meta’s public statements and the code WIRED found is the central tension. Before the Thursday report, Stone dismissed the findings by writing that the company could not answer questions about how the system would work because “the feature does not exist.” Andrew Bosworth, Meta’s chief technology officer, called the reporting “incredibly misleading” and “absolutely dishonest.” Yet the code was functional enough to include three AI models, one to detect faces, another to crop them, and a third to encode them as biometric data, all embedded in the companion app for a product already at the centre of a mounting privacy crisis.

Meta declined to answer ten questions WIRED posed before publishing, including whether it had already created the database of face profiles NameTag uses, how long the app retains photographs and biometric data of unrecognised people, and whether that data would ever be sent back to Meta’s servers. The company also did not respond to questions about whether it was building NameTag for blind or low-vision users, or to criticism from privacy advocates who warned the system could let stalkers and abusers identify strangers in public.

NameTag first surfaced in February, when The New York Times, citing internal Meta documents, reported that the company was developing face recognition for its smart glasses and considering a launch as early as this year. One internal memo reportedly described releasing the feature during a “dynamic political environment” when privacy and civil liberties advocates would be distracted by other concerns. WIRED subsequently found that much of NameTag’s machinery had been built into the Meta AI app as early as January, months before any public acknowledgement, adding another layer to the company’s pattern of shipping first and disclosing later when it comes to its smart glasses.

Kade Crockford, director of the technology for liberty programme at the American Civil Liberties Union of Massachusetts, said the removal does not undo the original decision to ship the code and pointed to it as evidence that consumer privacy needs stronger legal protection than Congress has been willing to provide. The Massachusetts House of Representatives last week unanimously passed a consumer privacy bill that, if enacted as written, would impose strong enforcement provisions including a private right of action allowing aggrieved users to sue. “State lawmakers need to do their job and step up to protect consumer privacy,” Crockford said.

Meta’s sneaky tactics in slipping the face-recognition code into its smart glasses show exactly why data privacy bills need the teeth of strong enforcement,” Crockford added. “Companies like Meta prioritise their bottom line, so lawmakers need to speak in the only language its C-suite understands.” Whether a code removal prompted by investigative reporting constitutes a victory or merely a tactical retreat depends on what Meta does next, and on whether the regulatory pressure building on both sides of the Atlantic produces enforceable consequences before the feature quietly returns under a different name.



Source link