LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › Evite Data Breach (2013)

CRITICAL severityConfirmedHow we verify

Evite Data Breach (2013): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·August 11, 2013

SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Evite Data Breach (2013)

Reported August 11, 2013. Approximately 101.0M people affected.

CRITICAL
Severity
101.0M
People affected
7
Data types exposed
August 11, 2013
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Evite Data Breach (2013) (reported August 11, 2013) exposed Dates of birth, Email addresses, Genders and Names belonging to roughly 101.0M people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.

Severity & verification
CRITICAL severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the Evite Data Breach (2013) breach?
101.0M accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

In 2019, Evite disclosed that it had discovered unauthorised access to a database archive containing records from 2013. The incident affected 101 million unique email addresses, along with additional personal details for service members. The exposure included passwords stored in plain text.

Incidents involving archived user data from earlier years remain relevant because large volumes of personal information continue to circulate after initial collection. When such archives are accessed without authorisation, the consequences extend to individuals whose details were provided years earlier, often without ongoing visibility into how their information is stored or protected.

What happened

Evite identified the unauthorised access in April 2019 during an internal investigation. The access involved a database archive that dated back to 2013. The exposed records contained 101 million unique email addresses, the majority belonging to invitation recipients rather than registered members.

For individuals who had created accounts, the archive also included names, phone numbers, physical addresses, dates of birth, genders, and passwords stored in plain text. No further technical details about the method of access or the duration of the unauthorised activity have been disclosed publicly.

How a breach like this happens

Breaches involving older database archives often occur when retained data is not isolated from production systems or when access controls weaken over time. Attackers may obtain credentials through unrelated compromises, exploit configuration errors, or use stolen authentication material to reach backup or legacy storage.

Once inside, an attacker can copy large volumes of records without triggering immediate detection if logging and monitoring are limited. Organisations that keep historical data for operational or compliance reasons sometimes retain it longer than necessary or in formats that lack modern encryption standards, increasing the window during which the information remains accessible.

About Evite

Evite operates an online platform that allows users to create, send, and manage digital invitations for events. The service collects contact information from both account holders and the people they invite, resulting in large stores of names, email addresses, and additional personal details.

Because the platform facilitates social and professional gatherings, the data it holds can include information about individuals who never created an account themselves. A breach at such a service therefore affects both active users and a wider set of contacts whose details were entered by others.

The information in question

The disclosed records included dates of birth, email addresses, genders, names, passwords, phone numbers, and physical addresses. Passwords were stored in plain text rather than in hashed form.

Public statements have not specified whether other categories of information, such as payment details or event-specific notes, were present in the accessed archive. The exact scope of data accessed beyond the listed fields remains unconfirmed.

What's at stake

Individuals whose email addresses and names were exposed face an increased likelihood of receiving targeted phishing messages that reference past events or personal details. Passwords stored in plain text can be tested directly against other online accounts, raising the chance of credential stuffing if the same passwords were reused elsewhere.

For Evite, the incident highlights the long-term costs of retaining historical user data without strong protective measures. Affected people may experience repeated misuse of their information over years, while the organisation must manage remediation, regulatory inquiries, and loss of user trust.

What to do if you're exposed

Change passwords on Evite and any other accounts that use the same or similar credentials. Enable multi-factor authentication wherever available, and review account activity for signs of unauthorised access.

Monitor email accounts for unusual messages and consider using a password manager to generate and store unique credentials. Readers can run a free exposure scan of their email address against known breach data to check whether their information appears in this or other incidents.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

CompanyEvite security record
70/100
DoxxScan™ · Moderate doxx risk
C- 64Below-average record

1 reported incident on record.

See Evite’s full breach history →

More recent breaches

Astropid Data Breach (2013)December 19, 2013Torrent Invites Data Breach (2013)December 12, 2013Pixel Federation Data Breach (2013)December 4, 2013Vodafone Data Breach (2013)November 30, 2013

Latest breaches

Read GalaxyWarden’s full analysis of the Evite Data Breach (2013) →

Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram