MyRecon OSINTMedela
Behind the exposed accounts
In September 2026, Swiss medical device company Medela was the target of a ShinyHunters "pay or leak" extortion campaign .
Follow the story
On 7 September 2026, Medela was breached. 423,947 accounts were exposed, including email addresses, employers, job titles. MyRecon rates it 61/100, severe.
How the story unfolded
Open a step to read the detail. Missing dates stay unknown.
02Entry point
The published account does not explain the exact way the data was obtained.
03Discovery and disclosure
A separate discovery or company-disclosure date is not established by this feed record.
04Added to the breach catalogue
2026-09-30. This is the catalogue date, not necessarily the disclosure date.
05Reported outcome
423,947 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Email addresses, Employers, Job titles, Names, Phone numbers, Physical addresses, Salutations, Support tickets.
The distinction in this record is between professional contact information and an assumption about medical records. Have I Been Pwned's description says the addresses belonged predominantly to healthcare professionals, staff and leads. Its listed fields include employers, job titles and support tickets. That does not establish that patient histories or clinical records were exposed, and this entry should not be read as making that additional claim.
Support-ticket context can make a fraudulent follow-up more convincing than a generic message. A sender may mention a product, workplace or earlier enquiry and ask the recipient to open an attachment or change payment instructions. This is a plausible risk from the listed fields, not evidence that such a campaign has been observed in this incident. Verify an unexpected request using a contact route you already know rather than the number or link inside the message.
For an organization, the useful response is to identify which business addresses and support interactions are affected, inform the appropriate internal security contact, and preserve suspicious messages through the normal reporting process. Do not circulate the leaked dataset to colleagues to look for their names. A breach entry does not establish that your current account is compromised or that the affected service has reset its access controls.
The source describes an extortion campaign and publication of allegedly obtained data. It does not document the exact intrusion path. Keep that unknown separate from the published contact-data description; guessing an unpatched system or stolen credential would add a causal story the available record does not support.
The story behind the breach
In September 2026, Swiss medical device company Medela was the target of a ShinyHunters "pay or leak" extortion campaign . The data allegedly obtained in the breach was later published publicly and included 424k unique email addresses belonging predominantly to healthcare professionals, Medela staff and leads. The exposed data consisted primarily of corporate contact information, including names, physical addresses and phone numbers, with some records also containing associated support tickets.
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.
How did it happen?
The published account does not explain the exact way the data was obtained.
What was the motive?
In September 2026, Swiss medical device company Medela was the target of a ShinyHunters "pay or leak" extortion campaign .
Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.
What was the outcome?
423,947 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Email addresses, Employers, Job titles, Names, Phone numbers, Physical addresses, Salutations, Support tickets.
What was exposed, and why it matters
Email addresses
The address becomes a confirmed, active target, expect more phishing, better aimed.
Employers
Connects a personal account to a workplace, which is how attackers pivot from a person to a company.
Job titles
Identifies who has access to what, which is how targets for business email compromise are picked.
Names
Turns an anonymous address into an identified person, which is what makes targeted phishing possible.
Phone numbers
Enables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.
Physical addresses
Where someone actually lives. Combined with a name this moves the risk off the internet.
Salutations
Adds detail to a profile that can be assembled from several breaches at once.
Support tickets
Adds detail to a profile that can be assembled from several breaches at once.
What to do if you were in it
Questions people ask about this breach
Was my email address in the Medela 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 Medela breach?
email addresses, employers, job titles, names, phone numbers, physical addresses, salutations, support tickets. 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 7 September 2026. It was published to Have I Been Pwned on 30 September 2026, a gap of 23 days during which the data was already out.
Is the Medela 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?
423,947 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.