[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1u2aii6fymmgc":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":7,"domain":9,"breachDate":10,"addedDate":11,"publishedAt":12,"modifiedDate":13,"contentUpdatedAt":14,"source":15,"sourceUrl":16,"sourceUrls":17,"pwnCount":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":12,"affectedCountUnit":20,"hasEnglishDescription":4,"contentLocale":21,"availableLocales":22,"translations":24,"severity":27,"dataClasses":28,"description":37,"seoTitle":38,"seoDescription":39,"logoUrl":40,"isVerified":4,"isSensitive":41,"isSpamList":41,"isMalware":41,"company":42},"6a452308a20f867c8ba8e71a","utair","Utair 2019 Data Breach","utair.ru","2019-03-21T00:00:00.000Z","2025-12-26T04:28:29.000Z",null,"2026-09-19T17:08:19.658Z","2026-07-19T00:02:36.327Z","Third party breach","",[],401400,"known","unknown","en",[21,23],"tr",{"en":25,"tr":26},{"slug":7},{"slug":7},"High",[29,30,31,32,33,34,35,36],"Dates of birth","Email addresses","Genders","Loyalty program details","Names","Passport numbers","Phone numbers","Physical addresses","\u003Cp>The Utair data breach was recorded as an incident related to Russian airline customer data dating back to 2019 and becoming public in 2020. The dataset contained more than 401,000 unique email addresses; it included names, physical addresses, dates of birth, passport numbers, phone numbers, gender information, and loyalty program details. Due to the airline and travel context, these fields carry a high risk in terms of identity and travel fraud.\u003C\u002Fp> \u003Ch2>Leaking Data Types and Risks\u003C\u002Fh2> \u003Cp>The data types listed in this record are the fields Dates of birth, Email addresses, Genders, Loyalty program details, Names, Passport numbers, Phone numbers, and Physical addresses. Password or payment card fields are not listed; however, the presence of passport numbers, dates of birth, and loyalty program details may lead to targeting users in identity verification processes.\u003C\u002Fp> \u003Ch2>Airline and Travel Context\u003C\u002Fh2> \u003Cp>Airline customers may be accustomed to receiving messages about tickets, check-in, baggage, flight changes, loyalty points, visa documents, passport verification, and refunds. This normal travel communication makes it easier for fake messages to appear real. A message that reaches the user with the correct name, passport, or loyalty program context may be perceived as a real airline notification.\u003C\u002Fp> \u003Ch2>Passport and Loyalty Program Risk\u003C\u002Fh2> \u003Cp>The passport numbers field makes this record particularly sensitive. The passport number, along with date of birth, name, and physical address, can be misused in identity verification or travel document processes. Affected individuals should check unexpected ticket changes, visa support, document uploads, or passport verification requests through the airline’s known channels, not via the link in the message.\u003C\u002Fp> \u003Cp>The loyalty program details area increases the risk of loyalty account fraud. Flight miles, membership level, point usage, or campaign messages can be used to direct the user to a fake login page. Strong and unique passwords should be used for loyalty accounts, and point transfers and profile changes should be monitored.\u003C\u002Fp> \u003Cp>Phone and physical address fields allow attacks to be carried out via SMS, calls, and mail. Messages such as fake baggage fees, flight refunds, seat upgrades, passenger information updates, or urgent document requests require special attention. Messages requesting verification codes, payment cards, passport images, or additional personal information should be considered suspicious.\u003C\u002Fp> \u003Ch2>Verified Scope and Long-Term Impact\u003C\u002Fh2> \u003Cp>Although this breach is old, fields such as passport and date of birth retain their value for a long time. Even if some documents are renewed, past passport numbers, travel history, or loyalty account context can be used in social engineering. Users should not consider an old airline account insignificant and should also check travel and hotel accounts used with the same email address.\u003C\u002Fp> \u003Ch2>Necessary Precautions\u003C\u002Fh2> \u003Cp>Affected Utair customers should be cautious about messages related to flights, tickets, baggage, loyalty points, passport verification, visa documents, or refunds. Even if the message displays personal information correctly, transactions should be conducted through known official channels. Although this record does not contain a password, it poses a long-term identity and travel fraud risk due to the passport, date of birth, and loyalty program fields.\u003C\u002Fp> \u003Ch2>Long-Term Travel Account Risk\u003C\u002Fh2> \u003Cp>The long-term impact of travel context in the Utair record is important. Even if old passport or loyalty information is outdated, fraudsters can use it to gain trust. If the user has previously transacted with the same airline or affiliated agencies, messages coming with old ticket or points information may appear more convincing.\u003C\u002Fp> \u003Cp>Travel accounts often use email, phone, passport, and payment information together. Therefore, affected individuals should check not only their Utair account but also hotel, car rental, travel insurance, and other airline loyalty accounts used with the same email. Messages requesting passport verification or point transfers should especially be verified through an independent channel.\u003C\u002Fp> \u003Cp>For institutions, the Utair incident shows that passport and contact information should be protected as privileged data in airline loyalty programs. Old travel records and loyalty account history should not be kept unnecessarily for long periods.\u003C\u002Fp> \u003Cp>Passengers should also use the official channel for every alert that comes with travel documents.\u003C\u002Fp> \u003Cp>This approach reduces the risk of fraud.\u003C\u002Fp>","Utair 2019 Data Breach (401.4 Thousand Reported Records)","Utair 2019 Data Breach. 401.4 Thousand reported records are reported. Reported data: Dates of birth, Email addresses, Genders. Review the scope, risks, and…","\u002Fuploads\u002Flogo\u002Futair_ru.webp",false,{"name":43,"sector":44,"country":45,"website":9,"websiteArchiveUrl":16,"websiteStatus":16,"websiteCheckedAt":12},"Utair","Airline","Russia"]