← Back to timeline

Vodafone

Have I Been PwnedConfirmed breachAdded November 30, 2013Occurred November 30, 201356,021 accountsvodafone.isAll Vodafone breaches →
What was exposed
Credit cardsEmail addressesGovernment issued IDsIP addressesNamesPasswordsPhone numbersPhysical addressesPurchasesSMS messagesUsernames
What to do if you were affected
Worried your data is exposed?Take back control of your personal data with Literal.
Protect your data
Details
In November 2013, Vodafone in Iceland suffered an attack attributed to the Turkish hacker collective "Maxn3y". The data was consequently publicly exposed and included user names, email addresses, social security numbers, SMS message, server logs and passwords from a variety of different internal sources.
Frequently asked questions

What is the Vodafone data breach?

In November 2013, Vodafone in Iceland suffered an attack attributed to the Turkish hacker collective "Maxn3y". The data was consequently publicly exposed and included user names, email addresses, social security numbers, SMS message, server logs and passwords...

When did the data breach happen?

This data breach occurred around November 2013.

How many accounts were affected?

Around 56,021 accounts were affected.

What information was exposed?

Exposed data included Credit cards, Email addresses, Government issued IDs, IP addresses, Names, Passwords, Phone numbers and Physical addresses.

What should I do if I was affected?

Change your password for this account, and anywhere you reused it. Turn on two-factor authentication. Watch your card and bank statements for unfamiliar charges, and consider requesting a new card number. Place a fraud alert or credit freeze with the major credit bureaus to block new accounts opened in your name. Expect more phishing and spam at this address. Treat messages that reference this company with extra caution. Watch for text-message phishing and SIM-swap attempts on your phone number. Be wary of targeted scams that use your personal details to sound convincing.

View on source ↗
Related breaches