Maileva Data Breach: La Poste Mail Platform Hack Exposes 22 Million
La Poste subsidiary Maileva confirms an attacker stole the names and postal addresses of 22 million people whose mail went through its platform. Hospitals, labs and social landlords are notifying patients and tenants, and some stolen records include medical invoice details.
Threat card
- Threat type
- Data Breaches
- Disclosed
- Nov 14, 2026
- Affected
- Maileva (Docaposte, La Poste group) mailing platform: names and postal addresses of 22 million recipients; mail-tracking data for several thousand client organisations
The short version
- Maileva confirms identification data of 22 million people was stolen from its mailing platform, which serves several thousand client organisations in France.
- The confirmed core data is first name, surname and postal address; some clients report email addresses, tenant numbers and medical invoice details in the exposed mail-tracking data.
- Maileva suspended its services on 23 September 2026 after spotting suspicious activity and restored them on 29 September.
- No threat group has claimed the attack and no sale or leak of the data has been confirmed.
The Maileva data breach has exposed the names and postal addresses of about 22 million people in France. Maileva, the online mailing service of La Poste’s Docaposte unit, confirmed the theft after Le Monde reported it on 14 November 2026. The intrusion dates to September. Most victims never dealt with Maileva directly: they received letters from hospitals, laboratories and social landlords that used it. Expect targeted payment scams built on the leaked data.
What happened
An attacker accessed Maileva’s platform in September 2026 and stole identification data of 22 million people whose post was sent through it. Maileva says the confirmed data is first name, surname and postal address, that bank details were not compromised, and that it has notified the CNIL, filed a criminal complaint and informed every client organisation.
Maileva prints and posts letters for businesses and public bodies. Its clients include social housing providers, medical laboratories, hospitals and transport networks. According to Cyberattaque.org, internal documents count about 39 million mail references, which become 22 million distinct people after deduplication, spread across several thousand client companies.
Maileva frames individual notification as its clients’ job, since they are the data controllers. That is why patients and tenants are hearing about the breach from their landlord or lab, weeks after the intrusion.
Timeline
| Date (2026) | Event |
|---|---|
| 9 to 23 September | Hôpital Foch payment reminder letters later found in the exposed data are sent through Maileva. |
| 23 September, 07:00 | Maileva suspends its services after detecting suspicious activity on its systems. |
| 24 September | Maileva tells clients about unauthorised access attempts on some customer accounts and fraudulent mailing attempts; affected accounts are blocked and a complaint is filed. |
| 29 September | Docaposte says services are fully restored after a six-day outage. |
| 9 October | An occupational health service in Cornouaille confirms a third party accessed a Maileva mail-tracking database. |
| 28 October | Hôpital Foch is informed. |
| 2 to 9 November | Inovie/Novabio labs, Flandre Opale Habitat, Hôpital Foch and Altéal notify patients and tenants. |
| 14 November | Le Monde reports the breach; Maileva confirms 22 million people affected. |
| 15 November | Coverage notes La Poste has confirmed the attack to AFP, according to Security Affairs. |
How the attack works
Maileva has not disclosed the technical entry point, the attacker’s identity or how the data left its systems, and says it will not detail the technical circumstances. What the public record does show is the shape of the incident, and that shape matters for defenders.
Initial access: customer accounts
Maileva’s first client notice on 24 September described unauthorised access attempts against some customer accounts and fraudulent mailing attempts. That points at account-level abuse of the platform rather than a mass leak at that stage. Maileva blocked the affected accounts. Whether those accounts were the route to the larger data set is not disclosed.
Collection: the mail-tracking database
A client in Cornouaille later confirmed that a third party accessed a Maileva mail-tracking database. Per its notice, that store held civility, names, postal and email addresses, identifiers and the file names attached to each mailing. A tracking database like this indexes every letter sent for every client, which explains how one intrusion reached 39 million mail references across thousands of organisations.
Impact: context leaks through metadata
The confirmed core data is basic identity, but clients report richer fields. Flandre Opale Habitat says tenant numbers, housing details and some invoice amounts were involved, with letters going back up to ten years. Hôpital Foch reminder letters exposed invoice numbers, dates of care and amounts due. Cyberattaque.org warns that a document name or mailing context can indirectly reveal someone’s health situation, even when no medical record was taken.
MITRE ATT&CK mapping
The sources describe outcomes, not tooling, so this mapping is limited to behaviour they state.
| Tactic | Technique (ID) | How it was used here |
|---|---|---|
| Initial Access | Valid Accounts (T1078) | Unauthorised access attempts against Maileva customer accounts, reported 24 September. |
| Collection | Data from Information Repositories (T1213) | Access to the Maileva mail-tracking database holding recipient and mailing records. |
| Impact | Service Stop (T1489), as a defensive result | Maileva itself suspended services for six days to contain the activity. |
Who is behind it
Not yet attributed. No group has claimed the attack, and no sale or publication of the data on criminal forums has been confirmed. A judicial investigation is under way. Security Affairs recalls that an earlier, separate attack on La Poste in 2025 was claimed by Noname057, but nothing links that group to the Maileva intrusion.
Affected products and versions
| Data types exposed | Records | Population affected |
|---|---|---|
| First name, surname, postal address (confirmed by Maileva) | About 39 million mail references | About 22 million distinct people |
| Civility, email address, identifiers, mailing file names | Mail-tracking database (per client notice) | Recipients of affected clients |
| Tenant numbers, housing details, invoice amounts | Letters up to ten years old | Flandre Opale Habitat tenants |
| Invoice numbers, dates of care, amounts due | Payment reminders sent 9 to 23 September | Hôpital Foch patients, via collector Kiwee.care |
| Names and postal addresses | Lab mailings | Inovie network patients (Novabio, Labosud, Biopyrénées and others) |
Other named clients include Altéal, the IZILO transport network in Lorient and the occupational health service in Cornouaille. The list is not complete.
Indicators of compromise
No technical IOCs have been published, and none are expected from Maileva given its stated position. Behavioural signs to hunt instead sit on the victim side: unexpected payment requests or reminders that quote a real invoice number, tenancy reference or care date, letters or emails that claim to come from a lab, hospital or landlord and point to a new payment channel, and identity verification calls that already know a person’s full postal address.
Detection and hunting
Client organisations should pull their Maileva account audit logs for September 2026 and look for logins from unfamiliar IPs or devices, API keys used outside normal hours, and mailing jobs created or cancelled that staff did not initiate, which matches the “fraudulent mailing attempts” Maileva described. Check whether any of your users reused their Maileva password elsewhere.
Fraud and finance teams should flag inbound payments or bank detail change requests that cite invoice numbers from letters sent through Maileva. Contact centres should expect callers who know a customer’s address and tenancy or patient reference, and should not treat that knowledge as proof of identity.
Mitigation and response
- Get written confirmation from Maileva of which mailings, date ranges and fields from your account were in the stolen data.
- As controller, assess your own GDPR notification duty to the CNIL and to the people affected, and document the decision.
- Notify recipients in plain language and tell them how you will and will not ask for payment.
- Rotate Maileva credentials and API keys and require MFA for every user.
- Stop sending descriptive file names and unnecessary personal fields to print and mail providers; the file name alone can reveal health or financial context.
- Add mailing and print vendors to your third-party risk register with breach notification terms and data retention limits.
Analyst take
This is a classic aggregator breach. Maileva holds little sensitive data per person, but it sits between thousands of organisations and their correspondents, so one compromise reaches 22 million people, most of whom never chose the vendor. It follows the same third-party pattern we tracked in the Uber breach through Fireworks AI and the Maersk legacy system breach.
The real danger is the fraud that follows. A name and address plus a genuine invoice number or care date is enough to write a payment reminder that looks exactly like the real one. Hospitals, labs and landlords that used Maileva should assume their recipients will be targeted and get ahead of it with clear warnings now, before the data surfaces publicly.
What to do now
0 of 5 done
Questions readers ask
What data was exposed in the Maileva data breach?
Maileva confirms first names, surnames and postal addresses of 22 million people; some clients say email addresses, tenant numbers, file names and medical invoice details were also in the exposed data.
Was I affected by the Maileva breach?
You may be if a landlord, lab, hospital or other organisation sent you letters through Maileva; those organisations, not Maileva, are responsible for notifying you.
Were bank details stolen in the Maileva hack?
Maileva says bank details were not compromised, but criminals can use the stolen names, addresses and invoice details for convincing payment scams.
Sources
One short email when something serious breaks.
Threatspedia covers major cyber threats only, verified against primary sources. Read our editorial policy, or report a correction.


