[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1dkhlej1d9a37":3},{"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":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":13,"affectedCountUnit":20,"hasEnglishDescription":4,"contentLocale":21,"availableLocales":22,"translations":24,"severity":27,"dataClasses":28,"description":35,"seoTitle":8,"seoDescription":36,"logoUrl":37,"isVerified":4,"isSensitive":4,"isSpamList":38,"isMalware":38,"company":39},"6a452308a20f867c8ba8e768","Abrigo","Abrigo Business Contact Data Incident (2026)","abrigo","abrigo.com","2026-04-14T00:00:00.000Z","2026-05-14T03:37:50.000Z",null,"2026-07-29T11:13:00.741Z","Authenticated business-contact corpus","",[],711099,"known","email_identifiers","en",[21,23],"tr",{"en":25,"tr":26},{"slug":9},{"slug":9},"High",[29,30,31,32,33,34],"Email addresses","Employers","Job titles","Names","Phone numbers","Physical addresses","\u003Cp>\u003Cstrong>The 2026 Abrigo business-contact data incident\u003C\u002Fstrong> is a corpus public breach source catalogues with a structured date of April 14, 2026, and 711,099 unique emails. Reported fields are emails, employers, job titles, names, phones, and physical addresses. Passwords and financial-account data are not classes in this record.\u003C\u002Fp>\u003Cp>The 711,099 figure is not unique people, employees, customers, suppliers, companies, or notices. One person may have multiple work emails, one organization may have multiple people, and not every row necessarily contains every field. There is no local searchable person-level corpus.\u003C\u002Fp>\u003Cp>A record does not establish identity, a current employer or job title, employee or customer relationship, decision authority, phone or address ownership, field co-occurrence, a financial account, password, invoice approval, fraud, or misuse.\u003C\u002Fp>\u003Cp>Employer, role, phone, address, and business relationships must remain private. An invoice, payment-routing, compliance, or executive request quoting a correct title or supplier context does not authenticate the sender and should follow an independent official channel and the existing approval process.\u003C\u002Fp>","Abrigo Business Contact Data Incident (2026). 711.1 Thousand email identifiers are reported. Reported data: Email addresses, Employers, Job titles. Review the…","\u002Fuploads\u002Flogo\u002Fabrigo_com.webp",false,{"name":7,"sector":40,"country":41,"website":10,"websiteArchiveUrl":16,"websiteStatus":16,"websiteCheckedAt":13},"Financial Technology","United States"]