[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3k277uci2osxs":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":7,"domain":9,"breachDate":10,"addedDate":11,"modifiedDate":11,"contentUpdatedAt":12,"source":13,"sourceUrl":14,"sourceUrls":15,"pwnCount":16,"affectedCount":16,"affectedCountStatus":17,"affectedCountLowerBound":18,"affectedCountUnit":19,"hasEnglishDescription":4,"severity":20,"dataClasses":21,"description":23,"seoTitle":14,"seoTitleEn":24,"seoDescription":14,"seoDescriptionEn":25,"logoUrl":26,"isVerified":4,"isSensitive":4,"isSpamList":27,"isMalware":27,"company":28},"68e3266eda11adda48825194","doxbin-scrape","Doxbin Scrape Data Breach","doxbin.com","2025-01-24T00:00:00.000Z","2025-01-28T02:09:58.000Z","2026-07-18T23:49:40.127Z","Third party breach","",[],435784,"known",null,"unknown","High",[22],"Email addresses","\u003Cp>Doxbin Scrape is a sensitive record associated with email addresses collected from the doxing platform Doxbin in January 2025. The record contains approximately 435,000 email addresses and carries a higher privacy risk than normal email lists due to the nature of the platform.\u003C\u002Fp>\u003Cp>This record should be considered more as email addresses collected from content or account context on Doxbin rather than a user database breach. The canonical data class is only the email address; username, password, address, or dox content should not be assumed for this record.\u003C\u002Fp>\u003Ch2>Leaking Data Types and Risks\u003C\u002Fh2>\u003Cp>The data classes tracked in the Doxbin Scrape record should be considered as email addresses. Email addresses can be used for targeted phishing, password reset schemes, and account matching across different services.\u003C\u002Fp>\u003Cp>Associating an email address with a doxing service can increase the risk of targeted harassment, threats, phishing, or account investigation. Since the content on the platform is often published without the consent of third parties, this record also requires caution in terms of victim safety.\u003C\u002Fp>\u003Ch2>Verified Scope and Boundaries\u003C\u002Fh2>\u003Cp>This record is associated with the doxbin.com domain and the January 2025 scrape incident. The scope is limited to email addresses only. Passwords, usernames, physical addresses, phone numbers, or published dox content are not considered verified data classes for this record.\u003C\u002Fp>\u003Cp>Areas not present in this record should not be described as if they have leaked. Full payment cards, official identification, private messages, health data, bank information, device content, or data belonging to other platforms should only be included in the risk assessment if they are explicitly present in the record. The text is based on verifiable data classes and the known boundaries of the incident.\u003C\u002Fp>\u003Ch2>User Groups at Risk\u003C\u002Fh2>\u003Cp>People who have account or email visibility on Doxbin, victims whose email addresses may have appeared in doxing content, and users who use the same email address on social media or work accounts are at risk.\u003C\u002Fp>\u003Cp>Users who use the same email address on different services, reuse their old passwords, keep their nicknames the same across many communities, or do not separate their work and personal accounts are at higher risk. The risk in profile and data broker records arises from the combination of very different domains from a single account, creating detailed context about the person.\u003C\u002Fp>\u003Ch2>Urgent Measures to Be Taken\u003C\u002Fh2>\u003Cp>Users in the positive match field should enable a strong password and two-step verification on their email account, document threat or harassment messages, and, if necessary, contact the platform, email provider, or relevant security support channels.\u003C\u002Fp>\u003Cp>Users in the positive match area should renew their passwords on accounts where they use the same or similar passwords, enable two-factor authentication where possible, and check their recent sessions. Records that do not contain passwords but include contact, billing, address, or profile data should be monitored for unexpected calls, offers, support, billing, and verification messages.\u003C\u002Fp>\u003Ch2>Long-Term Security Strategies\u003C\u002Fh2>\u003Cp>In the long term, the habit of using a password manager, unique passwords, two-factor authentication, and removing unnecessary personal information from accounts reduces risk. Reusing the same email address across different platforms makes it easier to combine data from different breaches; using a separate email or alias for critical accounts can be considered.\u003C\u002Fp>\u003Cp>The risk in the context of doxing is not one-time. Users should reduce public email visibility, use a pseudonymous address, and regularly check old content that could pose a personal security risk.\u003C\u002Fp>\u003Ch2>Record Control and User Action\u003C\u002Fh2>\u003Cp>LeakData check indicates whether the queried email address is present in this record. A positive result does not necessarily mean that all data fields definitely belong to that user; however, it is a sufficient warning for precautionary measures. A negative result only indicates that there is no match in this dataset, and does not eliminate the possibility of appearing in other breaches.\u003C\u002Fp>\u003Cp>A positive result indicates that the email address was found in the Doxbin Scrape records. Although the data field is only an email, the result should be considered sensitive due to the context of the incident.\u003C\u002Fp>","Doxbin Scrape Data Breach (435.8 Thousand Reported Records)","Doxbin Scrape Data Breach. 435.8 Thousand reported records were reported. Reported data: Email addresses. Review the scope, risks, and protective steps.","\u002Fuploads\u002Flogo\u002Fdoxbin_com.webp",false,{"name":29,"sector":30,"country":31,"website":9,"websiteArchiveUrl":14,"websiteStatus":14,"websiteCheckedAt":18},"Doxbin Scrape","Doxing Platform","Global"]