UTair Aviation Data Breach (2019)
Russian airline providing passenger and cargo air transport.
What this rating measures
The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.
It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.
Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Childhood minimum is an observed minimum on data that includes children; read it as a low floor, because the rating does not yet count how long a child carries the exposure. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →
Includes data that cannot be reissued or taken back. A changed password does not reach it.
- Circulating
- 401,400 email addresses
- Field types
- 8 seen
- Breach date
- Not established
- Observed as of
- Nov 17, 2026
- Attributed
- Unknown (server misconfiguration; data circulated then sold)
Breach date not established11 months laterListed in breach cataloguesObserved · scored
What data was exposed
How this data can be used against you
Identity
Enough identity detail to impersonate someone or open accounts in their name.
Physical targeting
Links a named person to where they live or go.
Social engineering
Contact details plus enough context for a convincing approach.
Account access
No usable login material in what circulates.
Financial
No usable financial detail in what circulates.
Coercion
Nothing in what circulates is sensitive enough for leverage.
Health
No medical detail in what circulates.
Crypto
Nothing in what circulates is tied to crypto assets.
Three key actions to take
Assume your home address is findable
Be wary of unexpected visitors, deliveries or messages that mention where you live. Ask people-search sites to remove your address, and check again every few months, because listings come back.
Ask about a new ID number
Your state DMV may issue a new driver's license number after a breach. Watch for accounts opened in your name.
Lock your mobile number
Ask your carrier for a port-out PIN so no one can move your number to a new phone.
Check whether you were affected
Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.
Talk to us about your exposure
If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.
Request a confidential call →The full breach analysis
What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.
- What happened
- Recent developments
- Reported and circulating
- Data points exposed
- Downstream risk
- Principal risk advisory
- Threat actor
- Background
- Data context
How this breach happened
A data breach affecting Russian airline Utair traces to early 2019, when a MongoDB database operated by the airline's in-house IT division, UTair Digital, was left exposed on the public internet from about January 21 to March 21, 2019. The database was identified by Russian leak-intelligence service DLBI, which notified the airline. Utair contained the exposure and characterized it as the result of a server misconfiguration.
The data initially circulated among threat-actor circles, was offered for sale in August 2019, and was published openly on a hacker forum in August 2020. Have I Been Pwned indexed about 401,000 unique email addresses associated with the dataset and added the breach to its public database in late 2025. Exposed fields included passenger names in both Cyrillic and Latin characters, email addresses, phone numbers, birth dates, gender, home addresses, passport numbers, and UTair Status loyalty program details including accumulated miles and tier level.
What has happened since the breach
Utair has continued to operate through the political and economic disruption that followed Russia's 2022 invasion of Ukraine, although Western sanctions have constrained access to international markets, aircraft parts, and certain digital services. Russian aviation more broadly has been the subject of a growing number of cybersecurity incidents linked to pro-Ukrainian hacktivist groups, including a major 2025 attack on flag carrier Aeroflot. Utair has not been publicly tied to a similar large-scale incident in the years since the 2019 leak. The 2019 dataset was added to public breach-tracking databases including Have I Been Pwned in late 2025.
What was reported vs. what is circulating
Reported
- Status
- Not yet researched
Circulating
- Observed as of
- Nov 17, 2026
- Breach date
- Not established
- Volume
- 401,400 email addresses
- Fields seen
- 8date of birth, email address, gender, loyalty program details, full name, passport number, phone number, home address
The score is built only on what is seen circulating.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Circulating |
|---|---|---|---|
| Date of Birth | Lasts for years | No | Yes |
| Email Address | Lasts for years | No | Yes |
| Gender | Fades over a few years | No | Yes |
| Loyalty Program Details | Lasts for years | No | Yes |
| Full Name | Lasts for years | No | Yes |
| Passport Number | Lasts for years | No | Yes |
| Phone Number | Fades over a few years | No | Yes |
| Home address | Lasts for years | No | Yes |
Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.
How attackers can use this data
Exposure enables travel fraud, phishing, booking impersonation, and physical-world targeting. Itinerary data can also reveal movement patterns and likely absence from home.
Risks for executives and other high-profile people
A travel or hospitality breach: itinerary, loyalty and contact data supports pattern-of-life inference and travel-themed phishing. For a high-profile principal this is targeting-grade, not merely identity-theft-grade: the combination lets an adversary locate, impersonate, or pressure the principal with little additional work.
Who is behind this breach
Attributed to Unknown (server misconfiguration; data circulated then sold).
About the company
UTair Aviation is a Russian airline based in Surgut, providing passenger and helicopter services across Russia and a smaller set of international destinations. Founded in 1967 and one of Russia's larger carriers by helicopter fleet, the airline operates regional and medium-haul passenger flights alongside extensive helicopter operations supporting the energy sector and emergency services. The carrier maintains a customer loyalty program known as UTair Status and runs its own digital systems through an in-house IT division, UTair Digital. Its passenger base is concentrated in Russia and the Commonwealth of Independent States.
Why the company holds this data
Commercial airlines collect passenger identity, contact details, booking records, payment-adjacent information, itinerary data, loyalty accounts, and support interactions across travel operations.
About this record
No reported total is on record for this breach. The circulating figure, 401,400 email addresses, is what has been observed in the published data. Circulation was last verified on Nov 17, 2026. The rating was last computed on Nov 17, 2026. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.