Is RingCentral Contact Center Voice safe?
RingCentral Contact Center Voice embeds a hardcoded OAuth client secret used to authenticate token requests to the RingCentral platform API.
The extension bundles a plaintext RingCentral OAuth client ID and client secret directly in its JavaScript. These credentials are used to construct a Base64-encoded Basic Authorization header sent with OAuth token requests to platform.ringcentral.com. Any party with access to the extension package can extract and reuse these credentials to authenticate against the RingCentral API.
Who publishes itRingCentral, Inc. - 9 other listings from the same operator, none carrying a finding
RingCentral, Inc. - 9 other listings from the same operator, none carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
9 other listings published from this account, 235k+ users between them, none of them carrying a finding.
Shared hosts - 2 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed RingCentral Contact Center Voice contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- platform.ringcentral.com
RingCentral Contact Center Voice sends data to platform.ringcentral.com. No other extension we have analyzed sends data here.
