[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3mprc754oityb":3,"$fh65i0m5jpdym":58},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":13,"modifiedDate":13,"contentUpdatedAt":13,"source":14,"sourceUrl":15,"sourceUrls":16,"pwnCount":19,"affectedCount":19,"affectedCountStatus":20,"affectedCountLowerBound":21,"affectedCountUnit":22,"hasEnglishDescription":4,"contentLocale":23,"availableLocales":24,"translations":34,"severity":45,"dataClasses":46,"description":50,"seoTitle":8,"seoDescription":51,"logoUrl":52,"isVerified":53,"isSensitive":53,"isSpamList":53,"isMalware":53,"company":54},"6a7221cfaff3cc04021f05b9","TicketIQ2016","Filtración de datos de TicketIQ de 2016 (15 475 cuentas afectadas)","ticketiq-2016","ticketiq.com","2016-03-01T00:00:00.000Z","2026-08-04T17:30:55.051Z","2026-10-10T08:24:34.896Z","Independent breach indexes","https:\u002F\u002Fleakedsource.com\u002Fbreaches\u002Fticketiq-data-breach-51f0ebd0",[15,17,18],"https:\u002F\u002Fdata-wells.niamonx.io\u002Fapi\u002Fbreach\u002FTicketIQ","https:\u002F\u002Fleakcheck.io\u002Fbreach\u002Fticketiq",15475,"known",null,"accounts","es",[25,26,27,28,23,29,30,31,32,33],"en","tr","zh","hi","ar","fr","bn","pt","ru",{"en":35,"tr":36,"zh":37,"hi":38,"es":39,"ar":40,"fr":41,"bn":42,"pt":43,"ru":44},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},"Medium",[47,48,49],"Email addresses","IP addresses","Geographic locations","\u003Cp>Un conjunto de datos de usuarios con aproximadamente 15 475 cuentas, atribuido a la plataforma estadounidense de reventa de entradas para eventos \u003Cstrong>TicketIQ\u003C\u002Fstrong> (anteriormente TiqIQ, ticketiq.com), apareció en LeakedSource y en directorios de filtraciones con fecha de marzo de 2016. Según lo informado, los datos incluyen direcciones de correo electrónico, ubicaciones geográficas y direcciones IP.\u003C\u002Fp>\u003Cp>TicketIQ no ha confirmado ninguna comunicación oficial sobre el incidente ni ninguna documentación presentada ante un organismo regulador. El conjunto de datos procede de archivos de filtraciones de terceros y su atribución está clasificada como no verificada.\u003C\u002Fp>","La filtración de TicketIQ de 2016 afectó a 15 475 cuentas. Consulte la fecha del incidente, los tipos de datos confirmados y qué medidas prácticas puede tomar.","\u002Fuploads\u002Flogo\u002Fticketiq-2016.webp",false,{"name":55,"sector":56,"country":57,"website":10,"websiteArchiveUrl":57,"websiteStatus":57,"websiteCheckedAt":21},"TicketIQ","Event Ticketing & Entertainment","",{"success":4,"breaches":59},[60,67,74,81],{"slug":61,"title":62,"companyName":63,"logoUrl":64,"breachDate":65,"affectedCount":66,"affectedCountStatus":20},"medela","Medela Filtración de datos","Medela","\u002Fuploads\u002Flogo\u002Fmedela.webp","2026-09-07T00:00:00.000Z",423947,{"slug":68,"title":69,"companyName":70,"logoUrl":71,"breachDate":72,"affectedCount":73,"affectedCountStatus":20},"dustin-group-2026-data-security-incident","Incidente de seguridad de los datos de Dustin Group en 2026","Dustin Group AB (publ)","\u002Fuploads\u002Flogo\u002Fdustingroup_com-6aaab48e5041e3a842fe832a-e26a53490c4a5cbe.webp","2026-09-03T00:00:00.000Z",1062841,{"slug":75,"title":76,"companyName":77,"logoUrl":78,"breachDate":79,"affectedCount":80,"affectedCountStatus":20},"elekta-2026-data-breach","Filtración de datos de Elekta en 2026","Elekta AB","\u002Fuploads\u002Flogo\u002Felekta-2026-veri-ihlali-afc72236a8ad.webp","2026-09-01T00:00:00.000Z",129576,{"slug":82,"title":83,"companyName":84,"logoUrl":85,"breachDate":79,"affectedCount":86,"affectedCountStatus":87},"novocure-2026-data-breach","Filtración de datos de NovoCure en 2026","NovoCure Limited","\u002Fuploads\u002Flogo\u002Fnovocure-2026-veri-ihlali-96b5c9defb8a.webp",1400,"lower_bound"]