Maileva Data Breach: La Poste Says 22 Million Hit

La Poste told AFP on November 14, 2026 that its subsidiary Maileva, a business mail-sending platform, lost the first names, last names and postal addresses of 22 million people in a mid-September attack. What is confirmed, what is not, and what teams that upload recipient lists to a mailing platform should check.

A tall, untidy stack of opened envelopes and papers in white, pink, green, yellow and purple, shot close up with a shallow depth of field
Photo by Alexander Grey on Unsplash

La Poste has confirmed that Maileva, its group’s online platform for sending business mail, lost the names and postal addresses of 22 million people in an attack in mid-September 2026. The company disclosed the figure to AFP on Saturday, November 14, almost two months after it took the whole platform offline. Bank details are not affected, according to La Poste. The affected people are mostly not Maileva’s customers but the recipients of letters those customers sent, which makes this a supply-chain data breach for thousands of French organizations.

What happened

Maileva is a subsidiary of Docaposte, itself part of the La Poste group. It describes itself as a “Plateforme spécialisée dans l’envoi de courriers pour les entreprises” (a platform for sending business mail) and claims more than 70,000 users and 180 million documents sent in 2024, according to Euronews.

On November 14, La Poste told AFP that Maileva “a été victime à la mi-septembre d’un vol des coordonnées de 22 millions de personnes” (was the victim in mid-September of a theft of the contact details of 22 million people), as reported by Euronews. In a written response published by Cyberattaque.org on November 13, Maileva said: “22 millions de personnes sont concernées par le vol de leurs données d’identification : prénom, nom, adresse postale” and “Plusieurs milliers d’entreprises clientes de Maileva sont concernées par cet incident” (several thousand Maileva business customers are concerned).

Timeline

Date (2026)EventSource
Mid-SeptemberData theft, per La PosteLa Poste via AFP/Euronews
September 23, 07:00Maileva suspends all services; tells clients of unauthorized access attempts by a cybercriminal seeking to send mail illegitimatelyDocaposte and Maileva client message, via Solutions Numériques
September 24Incident first reported publicly by Cyberattaque.org and FrenchBreachesSolutions Numériques
September 29Docaposte: services “de nouveau pleinement opérationnels” (fully operational again)Solutions Numériques
November 13Maileva’s written response puts the toll at 22 million peopleCyberattaque.org
November 14La Poste confirms the 22 million figure to AFPEuronews, Morocco World News

Confirmed vs not confirmed

ClaimStatusWho says so
Names and postal addresses of 22 million people stolenConfirmed by the companyLa Poste (AFP), Maileva (written response)
Bank details and other personal information not affectedCompany statementLa Poste (AFP)
Several thousand business customers affectedCompany statementMaileva
CNIL notified, complaint filed, judicial investigation openCompany statementLa Poste (AFP), Maileva
Attacker tried to use client accounts to send mailCompany statement (September)Maileva client message, Docaposte
About 39 million references deduplicating to ~22 million peopleNot confirmed publicly. Comes from internal documents attributed to DocaposteCyberattaque.org
Full contents of letters stolenNot reported. Cyberattaque.org notes the 22 million figure covers identity and address, not that every letter was takenCyberattaque.org (editorial analysis)
How the attacker got in (stolen passwords, missing MFA, a platform flaw)Not disclosedSolutions Numériques reports no new findings from Docaposte
Who did itNot attributed; no public claim foundNone of the sources reviewed

How the attack worked, as far as sources say

Very little is public. In September, Maileva told customers it had detected “des tentatives d’accès non autorisé par un cyber criminel afin de procéder à l’envoi illégitime de courriers” (unauthorized access attempts by a cybercriminal in order to send mail illegitimately), according to Solutions Numériques. Docaposte described “tentatives d’accès non autorisées à la plateforme”. The response reported at the time was to block the accounts concerned and stop the whole service as a precaution; Maileva also told individual customers that their own account had not been used and that no mail had been sent from their client space or API portal.

What is not public is the link between those access attempts and the data theft La Poste now dates to mid-September: whether the addresses were taken through compromised customer accounts, through the API, or from Maileva’s back end. We are not going to guess.

What it means for teams that use a mailing platform

Maileva’s model is common: a business uploads a document and a recipient list, and the provider prints, posts or sends it. The provider ends up holding a large, cross-customer store of names and addresses. Three things follow, whichever vendor you use.

You may be the one who has to notify. Maileva said: “L’information des personnes concernées relève des organisations clientes de Maileva” (informing the people concerned is up to Maileva’s client organizations). Under GDPR Article 33, “the processor shall notify the controller without undue delay after becoming aware of a personal data breach”, and the controller then has the 72-hour clock to the supervisory authority. If you use a mail or print-and-post service, check your contract’s breach-notification clause and who on your side receives that notice.

Lock down sending accounts like production credentials. The attacker’s stated goal was to send mail from customer accounts. A sending account can mail anyone in your name, so it deserves the controls you would put on a payments or email-sending API:

  • Turn on multi-factor authentication for every user of the portal, and remove shared logins.
  • Scope API keys to the minimum (send only, no address-book export if the vendor supports it), store them in a secrets manager, and rotate them after any vendor incident.
  • Restrict API access by source IP where the vendor offers it.
  • Ask for sending and login logs, and alert on sends outside your normal volume, hours or templates.

Minimise what sits at the vendor. Check how long the platform keeps uploaded recipient lists and sent documents, and delete or shorten retention where you can. A list that was purged after posting cannot be stolen months later. Our third-party SaaS vetting guide has a checklist for these questions.

Expect follow-on fraud. Names and postal addresses alone are useful for convincing phishing letters and calls that cite a real past letter from a known sender. If your organization sent mail through Maileva, tell customers how you will and will not contact them.

The pattern is the same one we saw when a single AI vendor breach exposed customer data at Notion and others: the incident is at the supplier, the obligations land on its customers.

Limits of this article

Two French outlets that reported the 22 million figure, Franceinfo and Ouest-France, could not be retrieved for this article. We rely on Euronews’s AFP-based report, Cyberattaque.org’s published Maileva response and Solutions Numériques’s September reporting. We did not retrieve a statement from Maileva’s or La Poste’s own websites. We will add a dated update if the company discloses the access method or the CNIL comments.

Sources and verification

Important claimSourceStatus
22 million people, mid-September theft, names and postal addresses, bank details not affected, CNIL and complaintEuronews via Yahoo Actualités, Nov 15 2026 (AFP)Verified (company statement as reported)
Maileva written response: 22 million, several thousand client companies, customers inform individualsCyberattaque.org, Nov 13 2026Verified (company statement as published)
39 million references from internal documentsCyberattaque.orgQualified (not confirmed by the company)
Sept 23 suspension, Sept 29 restoration, access attempts to send mail, accounts blockedSolutions Numériques, Sep 30 2026Verified (company statements as reported)
La Poste confirmed to AFP on Nov 14Morocco World News, Nov 15 2026, EuronewsVerified
Processor-to-controller notification dutyGDPR Article 33Verified
Access method, attributionNo sourceNot disclosed

Frequently asked questions

What data was stolen in the Maileva breach?

According to La Poste, quoted by AFP via Euronews, the exposed data is the first name, last name and postal address of the people concerned. La Poste says other personal information such as bank details is not affected. The people concerned are recipients of mail sent by Maileva's business customers, not necessarily Maileva account holders.

How many people are affected by the Maileva breach?

22 million people, according to La Poste and to a written response from Maileva published by Cyberattaque.org. Cyberattaque.org also reports that internal documents it attributes to Docaposte list about 39 million references that deduplicate to roughly 22 million people; that document figure has not been confirmed publicly by the company.

Who will notify people affected by the Maileva breach?

Maileva told Cyberattaque.org that all affected organizations were informed of the incident and that informing the people concerned is the responsibility of Maileva's client organizations. That matches the GDPR split in which a processor notifies the controller and the controller handles notification.

Who is behind the Maileva attack?

Nobody has been named. None of the sources we reviewed reports a claim of responsibility or an attribution, and the method of access has not been disclosed.

Hacking NewsMailevaLa PosteDocaposteData BreachGdprSaas SecurityThird-Party Risk