Skip to content
InYourGeek
visiteur@inyourgeek — shell
↹ compléter↑↓ historique⏎ ouvrirhelp
FR
← Back to the register

Peggy Sage

CriticalReportedRetail

Peggy Sage, a French cosmetics brand, was claimed in August 2025 by the DataCarry ransomware group, which said it had exfiltrated about 11.3 GB of data. On 8 October 2026, an archive of 106,455 files (13.86 GB uncompressed) attributed to this attack was made available. It reportedly contains hundreds of copies of identity documents, nearly 1,000 employee files, employment contracts, payslips, bank details and documents relating to health insurance and sick leave. The company has not confirmed the incident so far and the archive's contents have not been independently verified; those affected would mainly be current and former employees.

Identity documents combined with bank details and HR files could allow a malicious party to impersonate individuals or carry out targeted fraud, including banking fraud.

Disclosed on
October 8, 2026
Incident dated
August 15, 2025
Sector
Retail
Country
France
Cause
Ransomware

Exposed data

  • Full name
  • Identity document
  • Employment data
  • Banking data (IBAN, card)
  • Health data
  • Other personal data

You are only affected if you had an account or an order with this organisation.

What you can do

  • Watch your statements. On any unknown debit, block the card and request a refund — French law (art. L133-18) entitles you to it.
  • These documents enable identity theft, and cannot be reissued at will. Keep the notification letter: it proves where the leak came from if an account is opened in your name.
  • Health data is “special category” data under the GDPR: a leak opens a right to compensation, and the organisation must notify the DPA within 72 hours.
  • You can ask the organisation exactly what was exposed about you (right of access), and complain to the DPA if no answer comes within a month.

Sources

Entry built from the cited sources after a corroboration check, then reviewed before publication. Spotted an error, or have a correction? Write to us and the entry will be fixed. Contact