[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2r0xfrmulcqt2":3,"$f1h6pxceiqttfn":61},{"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":20,"affectedCount":20,"affectedCountStatus":21,"affectedCountLowerBound":22,"affectedCountUnit":23,"hasEnglishDescription":4,"contentLocale":24,"availableLocales":25,"translations":35,"severity":46,"dataClasses":47,"description":52,"seoTitle":53,"seoDescription":54,"logoUrl":55,"isVerified":4,"isSensitive":56,"isSpamList":56,"isMalware":56,"company":57},"6aad1b64aa9955ceb1371499","AnimeForum.ru 2017","AnimeForum.ru Data Breach","animeforum-2017","animeforum.ru","2017-12-08T00:00:00.000Z","2026-09-18T11:07:16.354Z","2026-10-10T10:36:34.492Z","2026-10-10T10:36:55.722Z","AnimeForum.ru community database dump & threat intelligence","https:\u002F\u002Fleakcheck.io\u002F",[16,18,19],"https:\u002F\u002Fsynscan.net\u002F","https:\u002F\u002Fransomlook.io\u002F",132515,"known",null,"unknown","en",[24,26,27,28,29,30,31,32,33,34],"tr","zh","hi","es","ar","fr","bn","pt","ru",{"en":36,"tr":37,"zh":38,"hi":39,"es":40,"ar":41,"fr":42,"bn":43,"pt":44,"ru":45},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},"High",[48,49,50,51],"Email addresses","Usernames","IP addresses","Dates of birth","\u003Cp>\u003Cstrong>The December 2017 AnimeForum.ru data breach\u003C\u002Fstrong> occurred when unauthorized threat actors breached the forum infrastructure of \u003Cstrong>AnimeForum.ru\u003C\u002Fstrong> (\u003Ccode>animeforum.ru\u003C\u002Fcode>), one of the prominent and longest-standing Russian-language online communities dedicated to anime, manga, cosplay, and Japanese pop culture. The compromise resulted in an unauthorized SQL database export of the community's Invision Power Board (IPB) member table (\u003Ccode>an_members\u003C\u002Fcode>), which subsequently circulated across cybersecurity repositories and credential monitoring databases.\u003C\u002Fp>\u003Ch2>What information was affected in the AnimeForum.ru incident?\u003C\u002Fh2>\u003Cp>The leaked forum export contains complete membership profiles across the enthusiast community. The incident compromised \u003Cstrong>132,515 unique user accounts\u003C\u002Fstrong>, exposing the following categories of personal information:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Account Identifiers:\u003C\u002Fstrong> Community usernames (name), member group identifiers, and forum rank titles.\u003C\u002Fli>\u003Cli>\u003Cstrong>Contact Credentials:\u003C\u002Fstrong> Canonical email addresses.\u003C\u002Fli>\u003Cli>\u003Cstrong>Network Identifiers:\u003C\u002Fstrong> Registration and activity IP addresses.\u003C\u002Fli>\u003Cli>\u003Cstrong>Demographic Details:\u003C\u002Fstrong> Registered birth dates (day, month, and year).\u003C\u002Fli>\u003Cli>\u003Cstrong>Temporal Metadata:\u003C\u002Fstrong> Account registration timestamps (joined) and forum participation metrics.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>Rigorous deduplication and RFC canonical verification confirmed \u003Cstrong>132,515 unique canonical email addresses\u003C\u002Fstrong> across the database dump.\u003C\u002Fp>\u003Ch2>Technical analysis and security risks\u003C\u002Fh2>\u003Cp>The incident involved an unauthorized export of the IPB core member roster. The exposed email addresses, usernames, and birth dates can support targeted phishing and account matching across services such as Steam, Discord, and VKontakte. Passwords are not among the fields listed in this record, so these data alone do not establish password exposure or enable credential stuffing. Accounts using a password reused elsewhere may still be at risk if that password has been exposed in a separate incident.\u003C\u002Fp>\u003Ch2>Recommended actions for affected users\u003C\u002Fh2>\u003Cp>Users who maintained accounts on AnimeForum.ru should:\u003C\u002Fp>\u003Cul>\u003Cli>Immediately change passwords on any existing accounts where their forum password was reused.\u003C\u002Fli>\u003Cli>Implement unique, strong passwords managed by a credential manager for each digital account.\u003C\u002Fli>\u003Cli>Activate multi-factor authentication (MFA \u002F 2FA) across personal email and digital entertainment platforms.\u003C\u002Fli>\u003C\u002Ful>","AnimeForum.ru Data Breach (132.5 Thousand Reported Records)","AnimeForum.ru Data Breach. 132.5 thousand records are reported. Reported data: Email addresses, Usernames, IP addresses. Review the scope, risks, and…","\u002Fuploads\u002Flogo\u002Fanimeforum.webp",false,{"name":58,"sector":59,"country":60,"website":60,"websiteArchiveUrl":60,"websiteStatus":60,"websiteCheckedAt":22},"AnimeForum.ru","Online Community","",{"success":4,"breaches":62},[63,70,77,84],{"slug":64,"title":65,"companyName":66,"logoUrl":67,"breachDate":68,"affectedCount":69,"affectedCountStatus":21},"cyberphoenix-community-2024","CyberPhoenix 2024 Data Breach","CyberPhoenix Community Veri İhlali (2024)","\u002Fuploads\u002Flogo\u002Fcyberphoenix-community-2024.webp","2024-09-19T00:00:00.000Z",419000,{"slug":71,"title":72,"companyName":73,"logoUrl":74,"breachDate":75,"affectedCount":76,"affectedCountStatus":21},"hackernewbie-2022","HackerNewbie Data Breach","HackerNewbie","\u002Fuploads\u002Flogo\u002Fhacker_newbie_org.webp","2022-09-10T00:00:00.000Z",28326,{"slug":78,"title":79,"companyName":80,"logoUrl":81,"breachDate":82,"affectedCount":83,"affectedCountStatus":21},"thctalk-2022","THCtalk Data Breach","THCtalk","\u002Fuploads\u002Flogo\u002Fthctalk.webp","2022-08-19T00:00:00.000Z",82013,{"slug":85,"title":86,"companyName":87,"logoUrl":88,"breachDate":89,"affectedCount":90,"affectedCountStatus":21},"trackitt-2022","Trackitt Data Breach","Trackitt","\u002Fuploads\u002Flogo\u002Ftrackitt_com.webp","2022-07-08T00:00:00.000Z",428360]