NIUS (Germany) July 2025 breach exposes 6k emails and payment details; added to Have I Been Pwned as sensitive
In July 2025, the German news service NIUS suffered a data breach whose data was subsequently leaked publicly. Have I Been Pwned added the dataset on 23 Aug 2026. It covers 6k unique email addresses along with names, physical addresses and payment details tied to purchases. HIBP flagged the breach as sensitive, so it is not publicly searchable and can only be checked by verified owners of the email address.
Technical Details
- Exposed data: email addresses, names, physical addresses, and payment details (IBANs or partial credit card data: masked card number, card type and expiry).
- The breach occurred in July 2025 and was later leaked publicly. The article does not state the initial access method or attribute the incident to any actor.
- This is a different incident from the Questel/ShinyHunters leak in the existing case; the only link is that both were added to HIBP.
Remediation
- Use a password manager to generate and store strong, unique passwords, and change any password reused across accounts.
- Enable 2FA wherever it is supported.
- Affected individuals should watch for fraud involving exposed IBAN or card details and for phishing that uses the leaked personal data.
Linha do tempo
-
NIUS (Germany) July 2025 breach exposes 6k emails and payment details; added to Have I Been Pwned as sensitive
ler a análise desta fonte ocultar
In July 2025, the German news service NIUS suffered a data breach whose data was subsequently leaked publicly. Have I Been Pwned added the dataset on 23 Aug 2026. It covers 6k unique email addresses along with names, physical addresses and payment details tied to purchases. HIBP flagged the breach as sensitive, so it is not publicly searchable and can only be checked by verified owners of the email address.
Technical Details
- Exposed data: email addresses, names, physical addresses, and payment details (IBANs or partial credit card data: masked card number, card type and expiry).
- The breach occurred in July 2025 and was later leaked publicly. The article does not state the initial access method or attribute the incident to any actor.
- This is a different incident from the Questel/ShinyHunters leak in the existing case; the only link is that both were added to HIBP.
Remediation
- Use a password manager to generate and store strong, unique passwords, and change any password reused across accounts.
- Enable 2FA wherever it is supported.
- Affected individuals should watch for fraud involving exposed IBAN or card details and for phishing that uses the leaked personal data.