[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f36pw51s0bht50":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"modifiedDate":13,"contentUpdatedAt":13,"source":14,"sourceUrl":15,"sourceUrls":16,"pwnCount":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":20,"affectedCountUnit":21,"hasEnglishDescription":4,"severity":22,"dataClasses":23,"description":31,"seoTitle":32,"seoTitleEn":33,"seoDescription":32,"seoDescriptionEn":34,"logoUrl":35,"isVerified":4,"isSensitive":36,"isSpamList":36,"isMalware":36,"company":37},"68e3266eda11adda48825197","Dubsmash","Dubsmash Data Breach","dubsmash","dubsmash.com","2018-12-01T00:00:00.000Z","2019-02-25T08:35:58.000Z","2026-07-29T11:40:53.262Z","Verified breach record","https:\u002F\u002Fwww.twingate.com\u002Fblog\u002Ftips\u002Fdubsmash-data-breach",[15,17],"https:\u002F\u002Fwww.theregister.com\u002Fsecurity\u002F2019\u002F02\u002F11\u002F620-million-accounts-stolen-from-16-hacked-websites-now-for-sale-on-dark-web-seller-boasts\u002F665817",161749950,"known",null,"unknown","Critical",[24,25,26,27,28,29,30],"Email addresses","Geographic locations","Names","Passwords","Phone numbers","Spoken languages","Usernames","\u003Cp>The Dubsmash data breach is a large-scale security incident recorded with the exposure of information belonging to accounts on a short video and messaging-focused social platform in December 2018. The verified scope includes 161,749,950 unique accounts. The breach date should be considered as December 1, 2018, and the addition to monitoring systems as February 25, 2019. The incident is significant because email addresses, usernames, and password data linked to social media profiles are found in the same dataset. This combination poses a serious threat in terms of account takeover attempts, password reuse risk, and personalized phishing messages.\u003C\u002Fp>\u003Ch2>Leaked Data Types and Risks\u003C\u002Fh2>\u003Cp>The verified data classes are email addresses, geographical location information, names, passwords, phone numbers, spoken language information, and usernames. It has been reported that the password field is associated with PBKDF2 hash values; nevertheless, the risk continues for weak or reused passwords. The appearance of the email address, username, name, and phone number together makes it easier for attackers to generate messages that identify the user. Location and language information can contribute to making targeted phishing messages appear more local and convincing. Therefore, the incident should not be seen as limited to an old social video account; if the same email or password was used on other services, it also poses a risk for current accounts.\u003C\u002Fp>\u003Ch2>Verified Scope and Boundaries\u003C\u002Fh2>\u003Cp>The Dubsmash record represents the video messaging platform incident from December 2018. The verified number of accounts should be used as 161,749,950. The data fields are email addresses, geographic location information, names, passwords, phone numbers, languages spoken, and usernames. The presence of password data in hashed form should be considered as a technical attribute of the password field, not as a separate data class. Payment card information, private message content, ID documents, or plaintext passwords are not among the verified fields for this particular record. The subsequent circulation of the incident alongside different breach packages does not mean that the record date has changed; the main breach period is 2018, and the verified addition date is 2019.\u003C\u002Fp>\u003Ch2>User Groups at Risk\u003C\u002Fh2>\u003Cp>The highest risk applies to people who use the email address associated with their Dubsmash account on other social media, email, shopping, gaming, or financial accounts. If the same username is used across different platforms, attackers can link the accounts together. Users with a phone number can be targeted through fake support calls, SMS scams, or account recovery messages. Although the risk appears lower for young users, accounts known for old video content, and people who have forgotten email addresses they no longer use, it still persists. The fact that the platform has later shut down or integrated with other services does not eliminate the value of identity information matches exposed in the past.\u003C\u002Fp>\u003Ch2>Urgent Measures to Be Taken\u003C\u002Fh2>\u003Cp>The affected user should first change the password used on their Dubsmash account and all other accounts where the same password is used. Email accounts, social media profiles, cloud storage, shopping accounts, and services with linked payments should be considered a priority. A unique password should be chosen for each service, and multi-step verification should be enabled wherever possible. Be cautious of fake notifications, account verification messages, and reward-based links received via phone number. Unknown sessions on social media accounts should be closed, connected apps should be reviewed, and recovery emails should be updated. If access to the old Dubsmash account is not possible, other accounts using the same email address should be checked more carefully.\u003C\u002Fp>\u003Ch2>Long-Term Security Strategies\u003C\u002Fh2>\u003Cp>In the long term, identity information used on social media and entertainment applications should be separated from main email and financial accounts. Using a password manager makes it easier to generate unique and strong passwords for each service. Email addresses used in old or closed applications should be reviewed regularly, and it should be ensured that the same password is not repeated elsewhere. In social applications that require phone number and location information, sharing should be kept to a minimum. Using the same username on many platforms increases the risk of account matching; therefore, different names can be preferred for different usage areas. From an institutional perspective, control processes that prevent employees from using passwords leaked from their personal social media in work systems are important.\u003C\u002Fp>\u003Ch2>Record Control and User Action\u003C\u002Fh2>\u003Cp>When a Dubsmash result is seen on LeakData, it is understood that the email address is included in the 2018 social video platform dataset. This result does not indicate that the user is actively using the same service today; however, it shows that past email, username, and password matches may be circulating. The user should first recall the passwords used during the same period and then check whether the same or similar password exists in other accounts. The email account and frequently used social media profiles should be examined first. The main period of the incident is December 2018, with a verified addition date of February 2019. This timeline prevents a false perception of the current event on the account security screen and accurately shows the real risk period.\u003C\u002Fp>","","Dubsmash Data Breach (161.7 Million Reported Records)","Dubsmash Data Breach. 161.7 Million reported records were reported. Reported data: Email addresses, Geographic locations, Names. Review the scope, risks, and…","\u002Fuploads\u002Flogo\u002Fdubsmash_com.webp",false,{"name":7,"sector":38,"country":39,"website":10,"websiteArchiveUrl":40,"websiteStatus":41,"websiteCheckedAt":42},"Social video platform \u002F Video messaging","United States","https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20220216012244\u002Fhttps:\u002F\u002Fdubsmash.com\u002F","archived","2026-07-29T11:30:22.391Z"]