[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3hq8t72hmd0ra":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":12,"modifiedDate":13,"contentUpdatedAt":14,"source":15,"sourceUrl":16,"sourceUrls":17,"pwnCount":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":18,"affectedCountUnit":20,"hasEnglishDescription":4,"contentLocale":21,"availableLocales":22,"translations":24,"severity":28,"dataClasses":29,"description":30,"seoTitle":8,"seoDescription":31,"logoUrl":32,"isVerified":4,"isSensitive":33,"isSpamList":33,"isMalware":33,"company":34},"5d4429632a3141b10666149d","RingCentral2026","RingCentral 2026 Data Breach","ringcentral-2026-data-breach","ringcentral.com","2026-07-28T00:00:00.000Z","2026-09-11T12:15:56.954Z","2026-09-11T14:24:11.628Z","2026-09-11T14:20:48.454Z","Official RingCentral security bulletin","https:\u002F\u002Fwww.ringcentral.com\u002Ftrust-center\u002Fsecurity-bulletin.html",[16],null,"unknown","people","en",[21,23],"tr",{"en":25,"tr":26},{"slug":9},{"slug":27},"ringcentral-2026-veri-ihlali","Unknown",[],"\u003Cp>\u003Cstrong>RingCentral disclosed the incident in a security bulletin dated July 28, 2026\u003C\u002Fstrong>, saying it had identified a sophisticated social-engineering campaign targeting the company. After detecting the activity, RingCentral said it promptly stopped the unauthorized activity and began an investigation with a leading third-party forensic firm. The bulletin did not state when the activity began, how long it lasted, or the precise access method, so July 28 is the disclosure date rather than a confirmed incident start date.\u003C\u002Fp>\u003Cp>The company said \u003Cstrong>data for a limited portion of RingCentral customers was affected\u003C\u002Fstrong> and that it was communicating directly with those customers. It did not name the affected organizations. The number of people or records involved and the categories of data concerned remain undisclosed.\u003C\u002Fp>\u003Cp>RingCentral drew a clear boundary around service impact: \u003Cstrong>the core RingCentral platform was not affected, and services continued without disruption\u003C\u002Fstrong>. The notice also states that customers who were not contacted by RingCentral were not affected. It therefore distinguishes data impact for notified customers from service availability for the broader customer base.\u003C\u002Fp>\u003Cp>RingCentral reported no new unauthorized activity after its remediation measures. The bulletin stated that customers did not need to take any action. The public account leaves the technical timeline and final data scope undisclosed. RingCentral said it stopped the activity, investigated with independent forensic support, and notified affected customers directly.\u003C\u002Fp>","RingCentral disclosed a July 2026 social-engineering incident affecting data for a limited portion of customers.","\u002Fuploads\u002Flogo\u002Fringcentral-2026-veri-ihlali-5d4429632a31.webp",false,{"name":35,"sector":36,"country":37,"website":10,"websiteArchiveUrl":38,"websiteStatus":38,"websiteCheckedAt":18},"RingCentral, Inc.","Cloud communications","United States",""]