Is SalesQL - B2B Email Finder safe?
SalesQL is low risk. On linkedin.com it fakes page visibility and focus, so LinkedIn cannot tell the tab is in the background. This defeats LinkedIn's check for automated use.
Who publishes itSALESQL LTD - no other listings under this identity
SALESQL LTD - no other listings under this identity
SalesQL findings
Extension makes LinkedIn think the tab is always open and in focus
On linkedin.com it fakes page visibility and focus, so LinkedIn cannot tell the tab is in the background.
This defeats LinkedIn's check for automated use.
What actually happens
You open any page on linkedin.com.
The match pattern covers all subdomains and all frames at document start.
The page is told the tab is visible and focused even when it is in the background.
Visibility getters, hasFocus and related events are overridden when the stored enabled flag is on.
What the page-context script changes
- visibilityStatevisible
Reads as visible unless the extension setting is off and the tab is backgrounded.
- hasFocus()true
Returns true whenever the focus setting is on, even if the tab is not active.
- Events suppressedvisibilitychange, blur, mouseleave
Real visibility, blur and mouse-leave events are stopped before page code sees them.
- Settings keysenabled, blur, focus, mouseleave, visibility, pointercapture
Stored flags that control each override; each defaults to on.
The code that does this
Visibility and focus overrides
Readable visibilityState getter
extracted/content/visibility/main.jsObject.defineProperty(document, "visibilityState", { get() { return port.dataset.enabled === "false" && port.dataset.hidden === "true" ? "hidden" : "visible"; }});Readable hasFocus proxy
extracted/content/visibility/main.jsDocument.prototype.hasFocus = new Proxy(Document.prototype.hasFocus, { apply(target, thisArg, args) { return (port.dataset.enabled === "true" && port.dataset.focus !== "false") || Reflect.apply(target, thisArg, args); }});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.
What SalesQL can do
Permissions this extension asks for, as declared in version 1.5.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on salesql.com
*://*.salesql.com/*
Read and change your data on linkedin.com
*://*.linkedin.com/*
See the address and title of every tab you have open
tabs
Store data in your browser
storage
Read and change cookies, including the ones that keep you signed in
cookies
SalesQL version history
1.2.70
Mar 4, 2026
+8 more
1.4.5
Sep 23, 2026
1.4.6
Oct 15, 2026
1.5.0
Oct 21, 2026
Chrome Web Store listing
- Versions
- 1.5.0 latest of 12 seen since March 4, 2026
- Store rating
- 4.8 from 654 ratings
- Last updated
- October 21, 2026
- Size
- 4.09 MiB
- Privacy policy
- salesql.com
