MyRecon OSINTAfD
Behind the exposed accounts
In September 2026, the German political party Alternative für Deutschland (AfD) suffered a data breach which exposed 345k unique email addresses.
Follow the story
On 9 September 2026, AfD was breached. 345,439 accounts were exposed, including email addresses, email messages. MyRecon rates it 35/100, moderate.
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-10-27. This is the catalogue date, not necessarily the disclosure date.
05Reported outcome
345,439 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Email addresses, Email messages.
The story behind the breach
In September 2026, the German political party Alternative für Deutschland (AfD) suffered a data breach which exposed 345k unique email addresses. The following month, hundreds of gigabytes of data containing hundreds of thousands of emails and attachments was published online, with searchable AI-generated summaries and downloadable original files.
An analysis of the incident reported that the breach was detected as early as 9 September, with a subsequent intrusion occurring five days later. In its public statement , AfD attributed the breach to an attack on a hosting provider, identified in subsequent reporting as the party-owned Alternita Dienstleistungs GmbH.
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?
345,439 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Email addresses, Email messages.
What was exposed, and why it matters
Email addresses
The address becomes a confirmed, active target, expect more phishing, better aimed.
Email messages
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 AfD 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 AfD breach?
email addresses, email messages. 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 9 September 2026. It was published to Have I Been Pwned on 27 October 2026, a gap of 48 days during which the data was already out.
Is the AfD 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?
345,439 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.