SOCLYDE logo
Current languageEN
Cybersecurity newscybersecuritymaileva

Maileva confirms a mail recipient data breach

Maileva confirms a breach affecting 22 million mail recipients. Check your sender’s notice for the data involved and verify unexpected payment requests.

Published on

By Soclyde

Two operators sort envelopes in a business mail processing room

In summary

  • La Poste confirmed a breach of names and addresses for 22 million recipients on November 15.
  • Document-related consequences need to be clarified by each business sending the mail.
  • Verify unusual letters or payment reminders with the sender through an established channel.

Explore next

Soclyde resources

Article contents

On November 15, 2026, La Poste confirmed that a mid-September cyberattack on Maileva exposed identifying data for 22 million mail recipients. Maileva, a Docaposte subsidiary, sends documents on behalf of businesses and institutions.

A breach at the mailing provider

The statement lists first names, surnames and postal addresses. La Poste says it notified France's data protection authority, filed a complaint and began informing affected business customers. It reports no alteration or destruction of data.

No destruction does not mean no disclosure. People may be affected without having created a Maileva account themselves: their relationship is with the organization sending a document.

Ask each sender about its own scope

La Poste refers to the relationship between its customers and their recipients for information contained in documents. It would therefore be inaccurate to describe the same medical, financial or administrative content as exposed for all 22 million people.

The Register obtained confirmation from La Poste and examined several customer notices. Those communications describe different situations. Check the notice from your own sender rather than extending one customer's circumstances to everybody.

Verify convincing letters

A correct name and address can make a reminder look credible without establishing its origin. Our recommendation is to independently find the usual number for the practice, landlord or business and confirm the reference and amount of any unexpected invoice.

Avoid paying through a link or QR code simply because a letter contains your details. Keep the message so the purported sender can check whether it is authentic.

Communicate about specific records

01net reports that France's specialist cybercrime police unit is handling the investigation and highlights difficulties in notifying recipients. If your small business uses Maileva, request the scope of your own mailings: dates, data categories and affected recipients.

Prepare a communication explaining what has been established for your records and provide a verifiable contact point. Do not ask customers to reply to an unexpected address with copies of sensitive documents.

Businesses managing access to mailing tools can use Soclyde to keep credentials in an encrypted vault on their devices. Premium sharing helps teams avoid scattering copies of access details across email conversations.

This benefit concerns credential management. It cannot erase data already exposed at Maileva or guarantee that a postal letter is authentic.

Key points

Read the sending organization's notice and independently verify unusual payment requests. To organize access protection for your business, contact Soclyde.

Frequently asked questions

What data does La Poste confirm?

Its November 15 statement lists first names, surnames and postal addresses for 22 million recipients. Other potentially exposed data depends on the documents and the businesses sending them.

Were all documents stolen?

The statement does not support that conclusion. Ask the organization that sent you mail for its own assessment of the data exposed and the consequences for you.

How should I handle a payment reminder?

Contact the business or institution using details you already trust. Your correct name and address in a letter do not provide sufficient proof that the request is authentic.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading