MyRecon OSINT
Assurance Retraite
On 1 September 2024, Assurance Retraite was breached. 70,372 accounts were exposed, including dates of birth, email addresses, family members' names. MyRecon rates it 53/100, serious.
The story behind the breach
In September 2024, the French national pension fund Assurance Retraite suffered a data breach affecting approximately 370k assistance beneficiaries . The data included 70k unique email addresses along with names, dates of birth, physical addresses, phone numbers, income levels, marital statuses, French social security numbers (NIR) and contact details of relatives or other nominated contacts. In its disclosure notice, Assurance Retraite attributed the breach to a compromised partner account .
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.
Read the original disclosure ↗
How did it happen?
The published account does not explain the exact way the data was obtained.
What was the motive?
The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.
Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.
What was the outcome?
70,372 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Dates of birth, Email addresses, Family members' names, Government issued IDs, Income levels, Marital statuses, Names, Phone numbers, Physical addresses.
What was exposed, and why it matters
- Dates of birthOne of the three things call centres ask to verify identity, and it never changes.
- Email addressesThe address becomes a confirmed, active target, expect more phishing, better aimed.
- Family members' namesAdds detail to a profile that can be assembled from several breaches at once.
- Government issued IDsPassport and licence numbers are used to prove identity to banks and telecoms, and they are effectively permanent.
- Income levelsAdds detail to a profile that can be assembled from several breaches at once.
- Marital statusesAdds detail to a profile that can be assembled from several breaches at once.
- NamesTurns an anonymous address into an identified person, which is what makes targeted phishing possible.
- Phone numbersEnables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.
- Physical addressesWhere someone actually lives. Combined with a name this moves the risk off the internet.
What to do if you were in it
- Move two-factor authentication off SMS and onto an authenticator app, which a SIM swap cannot intercept.
- Consider a credit freeze. A government identifier cannot be changed, so limiting what can be opened in your name is the only real control.
- Be sceptical of post and callers who already know your address, knowing it is no longer evidence of anything.
- Expect better-aimed phishing. A message that already knows your name and where you have an account is the whole point of a breach like this.
Questions people ask about this breach
Was my email address in the Assurance Retraite breach?
Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.
What data was leaked in the Assurance Retraite breach?
dates of birth, email addresses, family members' names, government issued ids, income levels, marital statuses, names, phone numbers, physical addresses. Each one is explained above, along with what it means for the person it belongs to.
When did it happen, and when did it become public?
The breach is dated 1 September 2024. It was published to Have I Been Pwned on 20 October 2026, a gap of 779 days during which the data was already out.
Is the Assurance Retraite breach real?
Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.
How many people were affected?
70,372 accounts. That is accounts rather than people, one person often has several.
Read next
Also in the archive
Case Files: how the landmark breaches actually happened →
Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.