Neteller Data Breach: What Was Exposed

What happened?

In May 2010, the e-wallet service known as Neteller suffered a data breach which exposed over 3.6M customers . The breach was not discovered until October 2015 and included names, email addresses, home addresses and account balances.

When did it happen?

The breach date in the public record is May 17, 2010. The record was added to the catalogue on November 30, 2015 and last updated there on November 30, 2015.

What information was reported as exposed?

Account balances
Dates of birth
Email addresses
Genders
IP addresses
Names
Phone numbers
Physical addresses
Security questions and answers
Website activity

These are incident-level categories. The record does not prove that every category was exposed for every affected person.

Who may be affected?

This record may be relevant to people who had an account or other relationship with Neteller or used neteller.com around May 17, 2010. A catalogue entry does not establish that every customer was affected or that every listed data category applied to each person. Compare the record with an official notice addressed to you.

What should you do?

Verify whether the notice applies to you

Compare the organization, dates, and information categories with any notice you received. Use contact details you independently confirm.

Secure affected accounts

Change exposed or reused passwords, begin with your email account, and turn on multi-factor authentication where available.

Protect identity information

Review your credit reports and consider a free credit freeze if identity information could support new-account fraud.

Expect targeted phishing

Treat unexpected breach follow-ups with caution. Do not use links or phone numbers in a suspicious message; contact the organization directly.

Choose actions that match the information involved. If you find signs that someone is using your identity, the Federal Trade Commission provides a personal recovery plan at IdentityTheft.gov.

Sources and review information

Page reviewed September 14, 2026 by the Data Breach Help Editorial Team. Catalogue details reflect the provider record and may change.

Editorial & sourcing policy Corrections policy