# 1.6 million RingCentral records leaked, and the entry point was one phone call

Source: https://startwithidentity.com/blog/2026-08-14-ringcentral-1-6-million-records-leaked-after-one-vishing-call/
Last updated: 2026-08-29
License: content by Start with Identity. Cite the source URL.

---

ShinyHunters breached RingCentral by voice-phishing an employee into handing over their password, claimed the intrusion on July 27, 2026 and said it had taken 623GB. RingCentral disclosed a breach from a social engineering campaign on July 28 and declined to pay. The group published a compressed 280GB archive on its leak site; Have I Been Pwned ingested the data on August 13 and confirmed roughly 1.6 million unique accounts containing names, email addresses, phone numbers and physical addresses. No vulnerability was exploited at any point in the chain, and RingCentral has not reported one.

## Why it matters

This is the same operator and the same opening move as the [McKesson breach](https://startwithidentity.com/blog/2026-08-28-mckesson-breach-vishing-okta-sso-salesforce-snowflake/) and the [EY incident](https://startwithidentity.com/blog/2026-07-27-shinyhunters-claims-ey-breach-via-stolen-third-party-credentials/): a phone call, a password, and no exploit anywhere in the chain. [Help desk and employee social engineering](https://startwithidentity.com/techniques/help-desk-social-engineering/) is now the dominant initial access route for this group, and the reason is arithmetic rather than sophistication. A vishing call costs minutes and works often enough.

The exposed data is the part worth planning around. Names, corporate email addresses and phone numbers for 1.6 million people, sourced from a communications provider, is a target list for the next round of the same attack. Verified phone numbers make the follow-on calls more convincing, which is how these campaigns compound.

A password that can be spoken aloud is the root cause, so the fix is a credential that cannot be: [phishing-resistant MFA](https://startwithidentity.com/glossary/phishing-resistant-mfa/) that produces no code a caller can request. Behind that, a help desk verification procedure that never relies on facts the caller supplies, and [step-up authentication](https://startwithidentity.com/glossary/step-up-auth/) on bulk data access so a single session does not export a terabyte quietly.

Sources: [BleepingComputer](https://www.bleepingcomputer.com/news/security/ringcentral-data-breach-exposed-info-of-16-million-accounts/), [The Register](https://www.theregister.com/cyber-crime/2026/08/14/16m-ringcentral-accounts-data-dumped-after-shinyhunters-extortion-attack/5288003)