[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f393irvg8m3fzk":3,"$f2qp848okhtxr7":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":20,"affectedCount":20,"affectedCountStatus":21,"affectedCountLowerBound":13,"affectedCountUnit":22,"hasEnglishDescription":4,"contentLocale":23,"availableLocales":24,"translations":34,"severity":45,"dataClasses":46,"description":55,"seoTitle":56,"seoDescription":57,"logoUrl":58,"isVerified":59,"isSensitive":59,"isSpamList":59,"isMalware":59,"company":60},"6aadd06f3a7f78608bb8d844","Vedomosti 2012","Vedomosti Alleged Data Exposure","vedomosti-2012","vedomosti.ru","2012-05-08T00:00:00.000Z","2026-09-18T23:59:42.881Z",null,"2026-10-10T10:43:35.594Z","Vedomosti Russian business daily newspaper MySQL database leak","https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FVedomosti",[16,18,19],"https:\u002F\u002Fwww.vedomosti.ru\u002F","https:\u002F\u002Ftherecord.media\u002F",217752,"known","email_identifiers","en",[23,25,26,27,28,29,30,31,32,33],"tr","zh","hi","es","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},"High",[47,48,49,50,51,52,53,54],"Email addresses","Passwords","Names","Usernames","Phone numbers","Employers","Job titles","Professional specializations","\u003Cp>\u003Cstrong>The 2012 Vedomosti data breach\u003C\u002Fstrong> occurred in May 2012 when the MySQL production user database (\u003Ccode>db_ved_users\u003C\u002Fcode>) of \u003Cstrong>Vedomosti\u003C\u002Fstrong> (\u003Ccode>vedomosti.ru\u003C\u002Fcode>), Russia's leading national business and financial daily newspaper, was compromised and exfiltrated.\u003C\u002Fp>\u003Ch2>What information was affected in the Vedomosti incident?\u003C\u002Fh2>\u003Cp>The leaked SQL database dumps (\u003Ccode>vedomosti.ru1.sql\u003C\u002Fcode> and \u003Ccode>vedomosti.ru2.sql\u003C\u002Fcode>) encompass corporate readers, subscribers, and journalists, exposing:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Identity & Profile Data:\u003C\u002Fstrong> Full names (first name, surname, patronymic) and platform nicknames.\u003C\u002Fli>\u003Cli>\u003Cstrong>Authentication Credentials:\u003C\u002Fstrong> User passwords stored completely in plaintext format.\u003C\u002Fli>\u003Cli>\u003Cstrong>Contact Coordinates:\u003C\u002Fstrong> Email addresses and personal or office telephone numbers.\u003C\u002Fli>\u003Cli>\u003Cstrong>Professional & Corporate Details:\u003C\u002Fstrong> Employer company names (company), industry specializations (comp_specialization), and corporate executive positions (comp_post).\u003C\u002Fli>\u003Cli>\u003Cstrong>Subscription Metadata:\u003C\u002Fstrong> Account registration timestamps (reg_date) and subscription flags.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>Strict RFC canonical email validation verified \u003Cstrong>217,752 unique valid email addresses\u003C\u002Fstrong> across the database dumps.\u003C\u002Fp>\u003Ch2>Technical analysis and security risks\u003C\u002Fh2>\u003Cp>The total absence of password hashing (plaintext storage) enabled immediate account compromise. The exposure of corporate executives, business analysts, and journalists alongside their active passwords creates severe exposure to credential stuffing, spear phishing, and corporate network penetration.\u003C\u002Fp>\u003Ch2>Recommended actions for affected individuals\u003C\u002Fh2>\u003Cp>Individuals who held accounts on Vedomosti should:\u003C\u002Fp>\u003Cul>\u003Cli>Immediately change passwords on all other platforms where the same password was utilized.\u003C\u002Fli>\u003Cli>Enable multi-factor authentication (MFA \u002F 2FA) across personal and enterprise accounts.\u003C\u002Fli>\u003C\u002Ful>","Vedomosti Alleged Data Exposure (217.8 Thousand Email Identifiers)","Vedomosti Alleged Data Exposure. 217.8 thousand email identifiers are reported. Reported data: Email addresses, Passwords, Names. Review the scope, risks, and…","\u002Fuploads\u002Flogo\u002Fvedomosti.webp",false,{"name":61,"sector":62,"country":63,"website":63,"websiteArchiveUrl":63,"websiteStatus":63,"websiteCheckedAt":13},"Vedomosti","Media","",{"success":4,"breaches":65},[66,74,81,88],{"slug":67,"title":68,"companyName":69,"logoUrl":70,"breachDate":71,"affectedCount":72,"affectedCountStatus":73},"gannett-2026","Gannett Data Breach","USA TODAY Co.","\u002Fuploads\u002Flogo\u002Fusa-today-co.png","2026-07-22T00:00:00.000Z",1,"lower_bound",{"slug":75,"title":76,"companyName":77,"logoUrl":78,"breachDate":79,"affectedCount":80,"affectedCountStatus":21},"success","SUCCESS Data Breach","SUCCESS","\u002Fuploads\u002Flogo\u002Fsuccess_com.webp","2026-03-04T00:00:00.000Z",253510,{"slug":82,"title":83,"companyName":84,"logoUrl":85,"breachDate":86,"affectedCount":87,"affectedCountStatus":21},"questo-morris-communications-2025","Questo and Morris Communications 2025 Data Breach","Questo Inc. \u002F Morris Communications Company","\u002Fuploads\u002Flogo\u002Fmorris_com.png","2025-10-01T00:00:00.000Z",11950,{"slug":89,"title":90,"companyName":91,"logoUrl":92,"breachDate":93,"affectedCount":94,"affectedCountStatus":73},"washington-post-oracle-ebs-2025","Washington Post Data Breach","The Washington Post","\u002Fuploads\u002Flogo\u002Fwashington-post.png","2025-07-10T00:00:00.000Z",862]