Maileva, the online mailing platform owned by La Poste’s digital arm Docaposte, has confirmed that the names and postal addresses of 22 million people were stolen in an intrusion dating to mid-September 2026. The people affected are mostly not Maileva customers. They are the recipients of letters sent through the platform by banks, landlords, hospitals and other organisations, which makes this a textbook third-party breach.
Incident overview: what happened and when
La Poste announced on Saturday 14 November that Maileva had been hit by a large-scale cyberattack in mid-September, and that the contact details of 22 million people had been stolen. The group followed with a written statement on Sunday 15 November, after the story had already spread in the press.
The affected individuals are described by the company as recipients of mail from Maileva’s corporate customers. They include people contacted by companies, landlords, hospitals and other bodies.
Maileva handles printing and dispatch of business mail, including registered letters, payslips and invoices. The company claims more than 70,000 users and 180 million documents sent in 2024. One caveat: Next reports the company claims more than 20,000 customers, including major French banks, insurers, SNCF, social landlords, medical laboratories and public institutions. The two figures measure different things (users versus customer organisations) and have not been reconciled publicly.
Timeline of the Maileva breach
| Date (2026) | Event | Source basis |
| 9 September | Start of the window for which one hospital says payment reminders were exposed | Hôpital Foch notice, via Next |
| 23 September, 7:00 | Maileva suspends all services after detecting unauthorised access attempts | Solutions Numériques / Docaposte |
| 24 September | Incident first reported publicly by Cyberattaque.org and FrenchBreaches, based on Maileva’s message to customers | Next, Solutions Numériques |
| 29 September | Docaposte says services are fully operational again | Solutions Numériques |
| 9 October | A Finistère occupational health service warns that the mail-tracking database was accessed without authorisation | Next |
| 3 and 6 November | A social landlord and Hôpital Foch warn recipients | Next |
| 14 November | La Poste confirms the 22 million figure to AFP | franceinfo |
| 15 November | Group statement published; Paris prosecutor confirms investigation | Next, franceinfo |
The platform was down from 23 September at 7:00, and Docaposte said the shutdown affected all customers. That means a six-day outage for 70,000-plus business users, a point with its own operational weight (see below).
What data was exposed
Confirmed by the company: first name, last name and postal address of 22 million people.
Reported as not affected: La Poste says bank details, passwords and social security numbers are not concerned. That claim comes through secondary reporting of the company’s position, so treat it as the company’s assertion.
Document content is a separate question. Maileva’s position is that the content of documents belongs to the relationship between its customers and their own recipients, and that affected customers were informed so they could warn recipients. That is a careful formulation, and in practice it means exposure beyond names and addresses is possible and varies by sender:
- Hôpital Foch told patients that the content of payment reminders sent between 9 and 23 September 2026 was exposed, including invoice number, date of care and amount due.
- Social landlord Flandre Opale Habitat warned that unauthorised access to personal data in letters sent over the previous ten years may have occurred, potentially including housing information or amounts on invoices.
- Earlier, the STC Quimper occupational health service said it had no evidence the contents of its documents were viewed or extracted, and that the incident involved access to the mail-tracking database.
These statements are not fully consistent with one another, which is normal in an unfinished investigation, but it means no one outside the investigation can yet say what share of the 22 million had document content exposed.
On the 22 million figure itself. Commentators have noted that 22 million recipients could mean 22 million letters, and therefore fewer unique people if the data spans several years. La Poste’s own wording is “personnes” (people). One secondary outlet reports that the affected database lists 39 million mail references; that number has not been confirmed by a primary source and should be treated with caution.
Root cause and attack methodology: what is known and what is not
Honest answer: the initial access vector has not been disclosed. La Poste has not communicated precisely on the intrusion method.
What the public record does support:
- Maileva’s early message to customers described a cybersecurity incident characterised by unauthorised access attempts to the platform, and the aim appears to have been sending fake letters. Docaposte was asked whether the attackers used stolen credentials, were let in by missing two-factor authentication, or exploited a platform flaw, and the answers reported so far do not settle it.
- Maileva’s message reassured each recipient that their own account had not been affected and that no mailing had left from their customer space or API portal.
- Press accounts describe a judicial investigation for “atteinte à un système de traitement automatisé de données,” entrusted to the Paris cybercrime brigade (BL2C).
- Per Next, Maileva states no alteration or destruction of data was observed.
One outlet reports that a document it saw says the attackers exploited an application flaw in Maileva’s production system, with suspicious activity beginning 9 September. We could not verify that document or its provenance, and no CVE has been published. It should be treated as an unconfirmed claim until Maileva, Docaposte, CNIL or investigators say so. The earlier signal of attempted fraudulent mailings and the later finding of mass data access may be two phases of one intrusion or two objectives; that too is unestablished.
Threat actors and attribution
No attribution has been made. We found no public claim of responsibility, no named group, and no official statement identifying a perpetrator for the Maileva breach.
Two other La Poste-related events should not be conflated with it:
- The December 2025 La Poste outage was a denial-of-service attack. It was claimed by the pro-Russian group NoName057(16), and La Poste said there was no impact on customer data. It is a different incident type (availability, not data theft), and nothing public links it to Maileva.
- On 3 October 2026, the Hauts-de-France Region announced that two suppliers, Atexo and Docaposte, suffered a cyberattack giving unauthorised access to personal data. That concerns the Génération#HDF student card platform, not Maileva, and no public source ties it to this breach.
Impact assessment
Individuals. Name plus postal address is not sensitive on its own, but it is exactly what physical-mail and phone fraudsters need. Where document content was exposed, as with the hospital reminders, the risk rises: a scammer who knows your invoice number, treatment date and amount owed can write a very convincing payment demand. Franceinfo-linked reporting also stresses that the affected people are mostly document recipients, not Maileva’s direct customers, so many may not recognise the vendor name when notified.
Business customers. Beyond the data, the six-day shutdown cut off a channel that legal deadlines can depend on. Solutions Numériques notes that for a lease termination notice, the deadline runs only from receipt of the registered letter.
Regulatory. Maileva says it notified CNIL, filed a complaint, and informed all affected companies as required. Under GDPR a processor must tell its controllers without undue delay, and controllers then handle regulator and individual notification. As commentators note, for a provider like Maileva it is generally the customers, as controllers of their own files, who must inform recipients. Whether CNIL opens a sanction procedure is unknown. Next also noted that the group only communicated openly after press coverage had built up, and the gap between the September detection and the 14 November confirmation will likely be scrutinised.
Financial and reputational. No loss figures have been published. We do not estimate any.
IT, OT, IoT and industrial cybersecurity implications
Be clear-eyed here: this is an IT and supply-chain incident. Nothing reported involves industrial control systems, SCADA, or IoT devices. Its relevance to OT Ecosystem readers is indirect but real.
- Industrial organisations rely on the same invisible vendors. Utilities, manufacturers and hospital operators send payslips, supplier invoices, bank-detail change notices and regulatory letters through outsourced print-and-mail platforms. A compromise there exposes workforce and supplier data even if the plant network is flawless.
- Account takeover on a mailing platform enables fraud. Cyberattaque.org, cited by Solutions Numériques, points out that a fake bank-detail change or invoice looks far more credible when sent through a channel customers already know. For industrial supply chains, that is business email compromise by post.
- Data retention is a risk multiplier. One landlord’s warning covered ten years of letters. Long retention of delivered-document metadata or content on a vendor platform widens the blast radius of a single intrusion.
- Concentration risk. Pooled platforms serving tens of thousands of organisations turn one weak control into a national-scale exposure.
(These are analytical points by the author, not findings of the investigation.)
Incident response and recovery
Confirmed actions: Maileva’s teams mobilised to secure the affected systems, according to La Poste; services were suspended on 23 September and restored on 29 September; CNIL was notified; a criminal complaint was filed; customer companies were informed; and the Paris prosecutor opened an investigation.
Not disclosed: containment details, forensic partners, whether credentials or keys were rotated, what controls changed, and whether the attacker’s access was fully removed beyond the platform restoration statement.
Security recommendations
For organisations that use outsourced mailing or document platforms
- Ask the provider for its breach timeline, root cause, and retention policy, and contractually require fast notification.
- Minimise what you send: avoid putting financial or health detail in the body of letters when a reference number works.
- Review retention. If a vendor keeps ten years of documents or tracking data, ask why.
- Enforce phishing-resistant MFA on every portal account and restrict API keys by scope and source IP; rotate keys after any provider incident.
- Monitor your own sending: alert on unusual volumes, templates, or destination patterns.
- Verify any bank-detail change or payment instruction out of band, by phone using a known number, no matter how legitimate the letter looks.
For service providers
- Segment tenants so one compromised account cannot reach another’s data; separate tracking metadata from document content.
- Detect and rate-limit bulk-send behaviour and mass reads.
- Encrypt stored documents with customer-scoped keys and expire them on a defined schedule.
- Prepare a tested notification playbook so controllers receive facts quickly.
For individuals who may be affected
- Expect fake letters, calls and texts that use your real name and address, and be sceptical of unexpected payment demands.
- Never share bank details, codes or passwords in response to an inbound contact; call the organisation on a number you already trust.
- If a hospital, landlord or employer has told you document content was exposed, follow their notice and watch for requests that reference that content.
- Bank details were reportedly not exposed, so there is no known need to change them on this basis alone.