People search VK (VKontakte) data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 4 VK (VKontakte)-linked incidents, with headline counts up to 390.4M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why VK (VKontakte) breach history matters
VK (VKontakte) operates in Social Media (Russia). Across indexed rows, recurring themes include third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — 500k accounts hijacked
Cataloged incident. Malware campaign hijacked over 500,000 VKontakte accounts through malicious Chrome extensions masquerading as VK customization tools. 'VK Styles' had ~400,000 installations. Extensions used multi-stage code injection, auto-subscribed users to attacker-controlled groups, reset account settings, manipulated CSRF tokens. Main extension removed from Chrome Web Store February 6, 2026. Exposed categories include Account access, subscription to attacker groups, account settings manipulation. BreachHistory cites approximately 500K+ affected records in this row. See the vk 2026 record and canonical BreachHistory entry.
2024 — 390M user profiles leaked
Unverified claim — treat actor counts cautiously. Hacker 'HikkI-Chan' leaked personal data of ~390 million VK users on Breach Forums. Dataset included full names, gender, profile picture URLs, country, city, and some email addresses. No passwords or phone numbers. Described as second-order breach from compromised third party; VK claimed data was scraped from public profiles. Exposed categories include Names, gender, profile URLs, location, some emails. BreachHistory cites approximately 390.4M+ affected records in this row. See the vk2024 and canonical BreachHistory entry.
2016 — 171M accounts sold dark web
Cataloged incident. VK (VKontakte) Russian social media platform had 171 million accounts hacked. Passwords, phone numbers, email addresses sold on dark web. Exposed categories include Email addresses, Passwords, Addresses, Phone numbers. BreachHistory cites approximately 171M+ affected records in this row. See the vk2016 and canonical BreachHistory entry.
2016 — — VK (VKontakte): Over 100m user accounts were hacked and the data…
Unverified claim — treat actor counts cautiously. Over 100m user accounts were hacked and the data put up for sale online. A VK spokesperson has denied that the site was breached, claiming the data for sale is old details no longer in use. BreachHistory cites approximately 100.5M+ affected records in this row. See the vku and canonical BreachHistory entry.
Patterns and analysis
- Third-party and supply-chain exposure — appears across multiple VK (VKontakte) catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the VK (VKontakte) company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/vk · Latest: vk2026.
Sources: BreachHistory catalog (4 rows for VK (VKontakte)), company and regulator disclosures cited in individual breach records.