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

Recent Breaches › AlpineReplay Data Breach (2019)

HIGH severityConfirmedHow we verify

AlpineReplay Data Breach (2019): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·August 27, 2019

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

AlpineReplay Data Breach (2019)

Reported August 27, 2019. Approximately 899K people affected.

HIGH
Severity
899K
People affected
7
Data types exposed
August 27, 2019
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The AlpineReplay Data Breach (2019) (reported August 27, 2019) exposed Dates of birth, Email addresses, Genders and Names belonging to roughly 899K 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
HIGH severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the AlpineReplay Data Breach (2019) breach?
899K 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 August 2019, reports indicated that AlpineReplay, a snow sports tracking application, had been subject to a data breach affecting 899,000 individuals. The exposed records included names, usernames, email addresses, genders, dates of birth, physical attributes such as weights, and passwords stored as unsalted MD5 or bcrypt hashes. Public detail on the precise timing, method of access, or total volume of records remains limited.

What happened

The breach was reported on August 27, 2019. Available information states that the incident exposed 899,000 unique email addresses along with associated account details. The service was later integrated into the Trace platform. No further technical specifics on how the data was obtained or the duration of exposure have been disclosed in public reporting.

How a breach like this happens

Data incidents involving consumer applications often result from unauthorized access to backend systems that store user records. Attackers may exploit vulnerabilities in application code, misconfigured databases, or compromised credentials to extract stored information. Once obtained, such data sets are sometimes posted or traded online. In cases where passwords are present, their storage format determines how readily they can be processed further.

About AlpineReplay

AlpineReplay operated as a mobile application focused on tracking snow sports activities such as skiing and snowboarding. Services of this type collect user profile information to support activity logging, performance metrics, and social features. The data types typically held include identifiers, contact details, and attributes relevant to physical activity. A breach at an organization handling this combination of personal and account data can affect users who registered for convenience features such as progress tracking or community sharing.

The information in question

The records named in connection with the incident include dates of birth, email addresses, genders, names, passwords, physical attributes, and usernames. Passwords were stored as either unsalted MD5 or bcrypt hashes. No additional categories of information have been confirmed as exposed. Organizations in this sector commonly retain profile data to enable core service functions, though the exact scope of the AlpineReplay data set remains unconfirmed beyond the listed fields.

Why it matters

Exposure of names, dates of birth, and email addresses can facilitate targeted phishing or account linkage across services. The presence of password hashes introduces a separate consideration: unsalted MD5 hashes are more susceptible to offline processing than bcrypt hashes, which incorporate deliberate computational cost. Users who reused credentials may face elevated risk of unauthorized access to other accounts. For the organization, the incident highlights the long-term consequences of retaining user data in older storage formats.

Were you affected?

Individuals who created an AlpineReplay account can review password hygiene across services and enable multi-factor authentication where available. Monitoring email accounts for unusual activity provides an early indicator of misuse. A free exposure scan of an email address against known breach data sets can indicate whether the address appears in publicly referenced records from 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

CompanyAlpineReplay security record
73/100
DoxxScan™ · Moderate doxx risk
B- 78Above-average record

1 reported incident on record.

See AlpineReplay’s full breach history →

More recent breaches

Sonicbids Data Breach (2019)December 30, 2019Go Ninja Data Breach (2019)December 17, 2019GameSprite Data Breach (2019)December 17, 2019Avvo Data Breach (2019)December 17, 2019

Latest breaches

Read GalaxyWarden’s full analysis of the AlpineReplay Data Breach (2019) →

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