Maileva: trace the letter through every provider
Maileva confirmed to reporters that identification data belonging to 22 million recipients was stolen. Notices from customer organizations show why each mailing workflow needs its own assessment.
Lire en portugaisBy Pentesty
Scope depends on which question you ask
In reporting published on November 13, Maileva said 22 million people had their first names, last names and postal addresses stolen. La Poste confirmed the scope to AFP on November 14. The figure counts recipients of customer organizations; separate evidence would be needed to count contracts or patients. The intrusion dates back to September; this editorial analysis is dated November 15, 2026.
The Hôpital Foch notice, published on November 6, describes a specific subset. The hospital uses Kiwee for payment reminders, with Maileva handling printing and mailing. Foch learned on October 28 that the content of letters in the September 9 through 23 window might have been viewed. They included invoice numbers, dates of care and amounts due. Those letters contained neither the nature of the care nor bank details.
Flandre Opale Habitat warned of potential exposure involving information in correspondence spanning up to ten years, depending on document type. Its notice stresses that this does not establish that each person’s data was accessed or used. Those subsets must remain connected to the organization and service that produced them.
Follow one mailing batch end to end
Consider a fictional payment reminder leaving a business system, passing through a customer service provider and reaching the postal operator. Record who contracts each stage, who receives the file and who transforms its content. A contract with the intermediary can leave the operations team without a clear view of the next provider handling the document.
Separate the addressee’s identity and address, processing metadata and the text of the letter. Ask which elements each participant actually receives and how long it needs them. Reconciling notices with datasets helps organize discrepancies; the starting point here is the mailing batch and its specific handoffs.
Test four points along the route
Use fictional documents and test accounts in an environment you own or one formally included in the authorized scope. Agree with the responsible teams on the results that demonstrate correct routing and the information that may be observed at each stage.
- Origin. Prepare a sample with a unique identifier and the minimum approved fields. Keep the document version, fictional recipient list and approval from the person responsible for the business process.
- Intermediary. Follow receipt of the sample and preparation of the next transfer. Match the identifiers used by both systems and check whether additional fields were included. Request only information covered by the assessed contract.
- Operator. Compare the authorized content with the preparation for printing or mailing. Preserve the processing receipt, relevant period and reviewer. A generic acknowledgement of receipt does not demonstrate which fields were processed.
- Return. Simulate a routing failure and check how its status reaches the originating system. Record the distinction between file acceptance, document processing and reported delivery, according to the assessed service’s capabilities and limitations.
Close the review by workflow
Genuine billing details can make a fraudulent request convincing. Confirm requests through an independently established contact. The payment beneficiary change analysis examines financial authorization in more detail; the mailing exercise should show how the team finds that channel without relying on the message it received.
At completion, deliver the observed route, confirmed fields and outstanding questions by mailing batch, period and provider. Retention and deletion require their own evidence, as discussed in our review of supplier-held copies. Investigation and communication owners can work from that defined scope, without assuming that every person had the same fields exposed.
Frequently asked questions
Are the 22 million people direct Maileva customers?
The figure the company supplied to reporters refers to recipients of mail sent by customer organizations. It does not represent 22 million contracting customers or establish how many patients were affected.
Was the entire content of every letter stolen?
The aggregate statement concerns names and postal addresses. Foch describes possible access to the content of certain payment reminders. Each organization needs to establish the relevant document and workflow.
Can a payment request with correct details be trusted?
Those details help identify an obligation, but do not prove that the sender has authority to request payment or change instructions. Confirmation must follow the channel previously established by the organization.
Does the exercise show how the intrusion happened?
It assesses the authorized workflow and results observed within the agreed environment. It does not reconstruct the Maileva incident or establish how systems outside the exercise behaved.
Sources and references
- Hôpital Foch: November 6 patient notice
- Flandre Opale Habitat: notice about mailing provider Maileva
- Cyberattaque.org: original reporting and Maileva written response
- AFP on TV5MONDE: company statement about 22 million recipients
Original Pentesty analysis, published November 15, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.