Is RocketReach Chrome Extension safe?
RocketReach is low risk. Dynamic analysis captured GETs to plugin.rocketreach.co/browser-extension/v1/rr-everywhere at startup, before login. It also fetches config from /v1/user/ff3p hourly, gating all-page activation, flippable externally by that host.…
Who publishes itRocketReach LLC - no other listings under this identity, 1 shared hostname
RocketReach LLC - no other listings under this identity, 1 shared hostname
Shared hosts - 1 hostname
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.
RocketReach findings
Remote Feature Flags Control Extension Behavior
Dynamic analysis captured GETs to plugin.rocketreach.co/browser-extension/v1/rr-everywhere at startup, before login.
It also fetches config from /v1/user/ff3p hourly, gating all-page activation, flippable externally by that host.
What actually happens
You open Chrome with RocketReach installed, even without logging in.
The extension contacts plugin.rocketreach.co to fetch feature flags that determine which capabilities are active on your browser.
This happens unconditionally on startup. The extension also repeats the fetch every 60 minutes via a Chrome alarm.
Captured request
HTTP 200 OK. Response JSON: {"enabled": false}. Captured during dynamic analysis, fired at startup before any login or user interaction.
What the remote flag responses control
- rr-everywhere toggle{"enabled": false}
Whether the extension activates on every website you visit, not just supported recruitment platforms.
- Feature flags store{"lastRefresh": 1744640400000, "features": {"new_profile_ui": true, "bulk_export": false}}
A JSON object stored in chrome.storage.local that gates which extension features are enabled for your account.
- ff3p config{"features": {"sidebar_v2": "enabled", "autocomplete": false}}
Third-party feature configuration fetched from /v1/user/ff3p, controls additional feature variants tied to your account.
The code that does this
Feature flag fetch and alarm registration from the minified source:
Alarm registration
// Registers a Chrome alarm named 'util.FeatureFlag' that fires every 60 minutes.async registerAlarm() { if (!chrome.alarms) return; if (await chrome.alarms.get(FeatureFlagService.AlarmName)) return; // already registered chrome.alarms.create(FeatureFlagService.AlarmName, { periodInMinutes: this._intervalMinutes }); // 60 min}rr-everywhere fetch
// Fetches whether the extension should activate on all sites.// Called unconditionally — no login check, fires on every extension load.async getAndSaveEverywhereState() { const url = new URL("/browser-extension/v1/rr-everywhere", this._apiService.BASE_URL); const response = await fetch(url, { method: "GET" }); const data = await response.json(); const isEnabled = data?.enabled ?? false; await this._setEverywhereState(isEnabled); // writes to chrome.storage.local}Feature flags fetch (ff3p)
// Fetches per-account feature flags. Requires login.// Also tracked with metric event he.ff3p ('endpoint:ff3p').async fetchFeatureFlags() { if (!(await this._authService.isLoggedIn())) return; const url = new URL("v1/user/ff3p?no_encode=true&inc1=true", this._apiService.BASE_URL); const response = await fetch(url); if (response.ok && response.status === HttpStatus.OK) { const data = await response.json(); await this._saveFeatureFlags(data); // stored at 'feature-flags' in chrome.storage }}Endpoints contacted for remote configuration
- plugin.rocketreach.co
Primary extension API. Serves the rr-everywhere toggle and per-account feature flags. Also the sole externally_connectable origin, so this host can message the extension directly.
RocketReach sends LinkedIn URL identifiers to its server to resolve profiles
Code analysis shows the extension takes the last path segment of a LinkedIn URL and requests it from plugin.rocketreach.co to get a public profile link.
Not confirmed by dynamic analysis.
What actually happens
You view a LinkedIn page whose address is not a public profile link.
The extension sends the last part of that address to plugin.rocketreach.co and receives a public profile ID.
The code that does this
Server-side URL resolution
Readable equivalent
assets/DomResolver-DprqD-wd.js// LinkedinUrlResolver, fallback when the URL is not already a public /in/ vanity URLasync resolveViaServer(record, store) { const identifier = lastPathSegment(record.url); // /linkedin.com/.../(id) const endpoint = new URL(`/browser-extension/v1/lr/${identifier}`, BASE_URL); const res = await fetch(endpoint, { method: "GET", headers: { "Extension-Version": VERSION } }); if (res.ok) { record.result = `https://www.linkedin.com/in/${(await res.json()).id}`; await store.markDomResolverRecordResolved(record, 200); }}What the request carries
- URL identifier/browser-extension/v1/lr/ACoAAB1x2Yk
The final path segment of the LinkedIn page you are viewing.
- Extension versionExtension-Version: 4.0.15
Sent as a header so the server knows the client build.
Destination
- plugin.rocketreach.co
Receives the LinkedIn identifier and returns a public profile ID.
Observation
Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.
Telemetry Sent on Every Extension Action
Dynamic analysis captured a POST from RocketReach's service worker to plugin.rocketreach.co/browser-extension/v1/m5s at startup, before use.
The base64 body decoded to metric events, flushed every 10s, tagged with endpoints like 'user'.
What actually happens
You install the extension and open Chrome.
The service worker begins queuing usage metric events and posts them base64-encoded to RocketReach's servers every 10 seconds.
No user interaction is required. Events are sent even before you log in or search for anyone.
Captured request
HTTP 200 OK (empty body). Captured during dynamic analysis, fired at startup before any user interaction.
- Content-Type
- text/plain;charset=UTF-8
eyJtZXRyaWNzIjpbeyJtZXRyaWNfdHlwZSI6ImluY3JlbWVudCIsIm5hbWUiOiJmZXRjaCIsInRhZ3MiOlt7InN0YXR1cyI6InN1Y2Nlc3MiLCJlbmRwb2ludCI6InVzZXIifV19LHsibWV0cmljX3R5cGUiOiJpbmNyZW1lbnQiLCJuYW1lIjoidXJsX3Jlc29sdXRpb24iLCJ0YWdzIjpbeyJzdGF0dXMiOiJub19tYXRjaCIsInBhZ2VfdHlwZSI6ImdlbmVyaWMifV19XX0=Why you can't catch this in DevTools
The POST body is base64-encoded, so it does not appear as readable JSON in browser DevTools or network monitors. Decoding the wire value reveals the full metrics array.
{ "metrics": [ { "metric_type": "increment", "name": "fetch", "tags": [ { "status": "success", "endpoint": "user" } ] }, { "metric_type": "increment", "name": "url_resolution", "tags": [ { "status": "no_match", "page_type": "generic" } ] } ]}Fields present in each metric event inside the batch
- Event typeincrement
Whether this is a count event (increment) or a measured value (histogram).
- Event nameurl_resolution
Which action or API call triggered the event, e.g. whether the extension tried to resolve the current page's URL.
- Tags: statusno_match
The outcome of the action, such as whether an API call succeeded or the URL matched a known profile page.
- Tags: endpointperson_search
Which RocketReach API endpoint was involved, reveals which features you used (person search, company search, user profile, etc.).
- Tags: page typelinkedin
What type of page you were on when the event fired (LinkedIn, recruiter portal, generic site).
The code that does this
The metrics service from the extension's minified source:
Metric type enum
enum MetricType { increment = "increment", histogram = "histogram",}MetricsService class (key methods)
class MetricsService { static async build(): Promise<MetricsService> { const svc = new MetricsService(); svc._apiService = await ApiService.build(); svc._endpointUrl = new URL("/browser-extension/v1/m5s", svc._apiService.BASE_URL); svc._featureFlags = await FeatureFlagService.build(); return svc; } encodedBody(): string { // base64-encodes the entire metrics batch — not encrypted, trivially reversible return btoa(JSON.stringify({ metrics: this._batch })); } _getBatchDelaysMS(): number { return 10000; // flush every 10 seconds }}Where metric data is sent
- plugin.rocketreach.co
Primary RocketReach API host. Receives the metrics batch at /browser-extension/v1/m5s. Sole permitted externally_connectable origin in the manifest.
Reproduce it yourself
Decodes a base64 metrics batch body from the RocketReach extension and prints it as formatted JSON. Paste the raw POST body from DevTools and run with Node.js.
- Node.js 14+
#!/usr/bin/env node// rocketreach-metrics-decoder.js// Decodes a base64-encoded metrics batch captured from RocketReach's// POST to plugin.rocketreach.co/browser-extension/v1/m5s//// Usage: node rocketreach-metrics-decoder.js <base64-string>// or: echo '<base64>' | node rocketreach-metrics-decoder.jsconst b64 = process.argv[2] || require('fs').readFileSync('/dev/stdin', 'utf8').trim();try { const json = Buffer.from(b64, 'base64').toString('utf8'); const parsed = JSON.parse(json); console.log(JSON.stringify(parsed, null, 2)); console.log(`\nTotal events in batch: ${parsed.metrics?.length ?? 0}`);} catch (err) { console.error('Failed to decode:', err.message); console.error('Expected: a base64 string from the POST body of /browser-extension/v1/m5s'); process.exit(1);}- 1Open DevTools Network tab with RocketReach installed.
- 2Filter by 'm5s'.
- 3Copy the POST body.
- 4Run: node rocketreach-metrics-decoder.js '<base64>'.
- 5Decoded metrics print to stdout.
+1 more finding not shown
RocketReach version history
3.0.71
Mar 4, 2026
+3 more
4.0.11
Jul 10, 2026
4.0.14
Aug 8, 2026
4.0.15
Aug 11, 2026
Where RocketReach sends data
- plugin.rocketreach.co/browser-extension/v1/…9 calls
From its background script · only this extension
- plugin.rocketreach.co/login1 call
From a script it injects into websites · only this extension
- rocketreach.co/login1 call
From a script it injects into websites · only this extension
Chrome Web Store listing
- Versions
- 4.0.15 latest of 7 seen since March 4, 2026
- Store rating
- 4.2 from 457 ratings
- Last updated
- August 11, 2026
- Size
- 325 KiB
- Privacy policy
- rocketreach.co
