Breach Database / Vodafone
Yes — Vodafone was breached.
- 56,021 accounts affected
- Breach occurred 2013-11-30 · vodafone.is
- Verified entry in the Have I Been Pwned catalog
What happened
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.
What data was exposed
- Credit cards
- Email addresses
- Government issued IDs
- IP addresses
- Names
- Passwords
- Phone numbers
- Physical addresses
- Purchases
- SMS messages
- Usernames
What to do right now
- Change your password for this service now. And change it anywhere you reused the same password — attackers try leaked passwords on other sites within hours ("credential stuffing").
- Turn on two-factor authentication. Even a leaked password is useless against an account protected by a second factor. Prefer an authenticator app over SMS.
- Watch your card and bank statements. Set up transaction alerts, and consider a card freeze or replacement if the exposure included full card numbers.
- Freeze your credit. A credit freeze at the major bureaus is free and blocks new accounts from being opened in your name.
- Be alert for smishing and SIM-swap attempts. Treat unexpected texts and "carrier" calls with suspicion; add a PIN/port-freeze with your mobile carrier.
- Watch for targeted phishing mail. A leaked home address makes postal and doorstep scams more convincing.
- Expect convincing phishing emails. Attackers use breached details to write personalized emails. Be suspicious of any message referencing this service.
- Check your other accounts on Have I Been Pwned. Your email address may appear in other breaches you don't know about yet.
- Monitor the apps you use going forward. Clearly watches the breach record for the companies behind your apps and alerts you the moment one appears.
Breach data from Have I Been Pwned. Listing here means the service appears in the public breach record — not that your personal data was affected.