[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f32p5ca4iloxct":3,"$fhsgmnhkufd84":64},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":13,"modifiedDate":14,"contentUpdatedAt":14,"source":15,"sourceUrl":16,"sourceUrls":17,"pwnCount":19,"affectedCount":19,"affectedCountStatus":20,"affectedCountLowerBound":13,"affectedCountUnit":21,"hasEnglishDescription":4,"contentLocale":22,"availableLocales":23,"translations":33,"severity":44,"dataClasses":45,"description":55,"seoTitle":56,"seoDescription":57,"logoUrl":58,"isVerified":59,"isSensitive":59,"isSpamList":59,"isMalware":59,"company":60},"6aae83ebff37edda2cc8b2b0","Loozap 2025","Loozap Alleged Data Exposure","loozap-2025","loozap.com","2025-12-23T00:00:00.000Z","2026-09-19T12:45:31.011Z",null,"2026-10-09T21:30:39.858Z","Loozap pan-African classifieds and social network SQL database dump","https:\u002F\u002Floozap.com\u002F",[16,18],"https:\u002F\u002Fbw.loozap.com\u002Fuser\u002Frecover",7156600,"known","email_identifiers","en",[22,24,25,26,27,28,29,30,31,32],"tr","zh","hi","es","ar","fr","bn","pt","ru",{"en":34,"tr":35,"zh":36,"hi":37,"es":38,"ar":39,"fr":40,"bn":41,"pt":42,"ru":43},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},"Critical",[46,47,48,49,50,51,52,53,54],"Email addresses","Names","Passwords","Phone numbers","Usernames","Genders","Dates of birth","IP addresses","Website activity","\u003Cp>\u003Cstrong>The 2025 Loozap data breach\u003C\u002Fstrong> occurred in December 2025 when the backend databases of \u003Cstrong>Loozap\u003C\u002Fstrong> (\u003Ccode>loozap.com\u003C\u002Fcode>), a major pan-African online classifieds and social networking platform, were breached and published online.\u003C\u002Fp>\u003Ch2>What information was compromised in the Loozap incident?\u003C\u002Fh2>\u003Cp>The leaked MySQL database dumps (\u003Ccode>lara237users.sql\u003C\u002Fcode>, \u003Ccode>Wo_Users.sql\u003C\u002Fcode>, \u003Ccode>DBlistings360_osclass777.sql\u003C\u002Fcode>, etc.) contain extensive user profiles and classified advertisement records. Verified exposed data classes include:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Identity &amp; Contact Details:\u003C\u002Fstrong> Full names, usernames, registered email addresses, and phone numbers.\u003C\u002Fli>\u003Cli>\u003Cstrong>Authentication Credentials:\u003C\u002Fstrong> Bcrypt and SHA-1 password hashes, along with password reset tokens.\u003C\u002Fli>\u003Cli>\u003Cstrong>Demographic &amp; Profile Data:\u003C\u002Fstrong> Genders, dates of birth, profile photos, and country\u002Flocation codes.\u003C\u002Fli>\u003Cli>\u003Cstrong>Network &amp; Activity Records:\u003C\u002Fstrong> Registration and last login IP addresses, timestamps, and website activity.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>RFC 5322 ASCII canonical verification confirmed \u003Cstrong>7,156,600 unique valid email addresses\u003C\u002Fstrong> across all user tables.\u003C\u002Fp>\u003Ch2>Security advisory &amp; protection measures\u003C\u002Fh2>\u003Cp>The exposure of usernames, email addresses, and password hashes creates risks of credential stuffing and targeted phishing. Impacted users should:\u003C\u002Fp>\u003Cul>\u003Cli>Immediately update passwords on other services where the same credentials were reused.\u003C\u002Fli>\u003Cli>Enable two-factor authentication (2FA) wherever available and monitor for suspicious communications.\u003C\u002Fli>\u003C\u002Ful>","Loozap Alleged Data Exposure (7.2 Million Email Identifiers)","Loozap Alleged Data Exposure. 7.2 million email identifiers are reported. Reported data: Email addresses, Names, Passwords. Review the scope, risks, and…","\u002Fuploads\u002Flogo\u002Floozap.webp",false,{"name":61,"sector":62,"country":63,"website":63,"websiteArchiveUrl":63,"websiteStatus":63,"websiteCheckedAt":13},"Loozap","Retail","",{"success":4,"breaches":65},[66,73,81,88],{"slug":67,"title":68,"companyName":69,"logoUrl":70,"breachDate":71,"affectedCount":72,"affectedCountStatus":20},"carhartt","Carhartt Data Breach","Carhartt, Inc.","\u002Fuploads\u002Flogo\u002Fcarhartt_com.webp","2026-08-13T00:00:00.000Z",12933413,{"slug":74,"title":75,"companyName":76,"logoUrl":77,"breachDate":78,"affectedCount":79,"affectedCountStatus":80},"family-farm-home-2026","Family Farm & Home Data Breach","Family Farm & Home","\u002Fuploads\u002Flogo\u002Ffamily-farm-home.png","2026-07-20T00:00:00.000Z",6,"lower_bound",{"slug":82,"title":83,"companyName":84,"logoUrl":85,"breachDate":86,"affectedCount":13,"affectedCountStatus":87},"lidl-online-shop-2026","Lidl Online Store 2026 Data Breach","Lidl","\u002Fuploads\u002Flogo\u002Flidl_com.svg","2026-07-13T00:00:00.000Z","not_disclosed",{"slug":89,"title":90,"companyName":91,"logoUrl":92,"breachDate":93,"affectedCount":94,"affectedCountStatus":20},"chick-fil-a-2026","Chick-fil-A 2026 Data Breach","Chick-fil-A","\u002Fuploads\u002Flogo\u002Fchick_fil_a_com.svg","2026-06-17T00:00:00.000Z",13322]