Is Amazon Product Finder - AMZScout PRO Extension safe?
AMZScout PRO is low risk.
AMZScout PRO keeps a WebSocket open to its server and runs server-pushed Amazon page fetches using your session.
The background worker connects to ws.amzscout.net and receives tasks telling it which Amazon product and review pages to fetch and parse. These requests include your Amazon cookies and run without any user interaction, and the parsed results are sent back to the server.
Who publishes itAMZscout Corp. - 6 other listings from the same operator, 2 of them carrying a finding
AMZscout Corp. - 6 other listings from the same operator, 2 of them carrying a finding
Same store account
6 other listings published from this account, 180k+ users between them. 2 of them carry a finding.
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.
AMZScout PRO findings
AMZScout background worker fetches Amazon pages on remote command
The background worker keeps a WebSocket open to AMZScout's server.
A server-sent "task" message with ASINs makes it fetch those Amazon pages directly, using site-wide access, whether or not Amazon is open in any tab.
What actually happens
AMZScout's backend sends a WebSocket message with event:"task" over the socket the background worker already has open.
No Amazon tab or user click is required; the worker connects on its own at startup.
The background worker builds Amazon product URLs from the message's ASINs and fetches those pages directly, using the extension's access to every site.
Parsed results are sent back over the same socket to AMZScout's server.
The code that does this
Background worker: WebSocket setup and command dispatch
Deobfuscated: connect() / keepAlive() / poller() / onMessage()
background.js value: function connect() { var t, r = this; chrome.storage.local.get(d, (function(o) { t = o && o["CALC_EXT-next-delay-run"]; var i = (new Date).getTime(), a = !t || t <= i; if ((!r.socket || r.socket.readyState !== WebSocket.OPEN) && a) { var c = chrome.runtime.getManifest(), u = c && c.version || void 0; r.socket = new WebSocket("".concat(y, "?software=").concat("SCOUT_EXT_PRO", "&version=").concat(u)), r.socket.onmessage = function(t) { return r.onMessage(t) }, r.socket.onerror = function(t) { return r.onError(t) }, r.socket.onopen = function(t) { return r.openConnection(t) }, r.socket.onclose = function(t) { return r.closeConnection(t) } } })) } }, { key: "keepAlive", value: function keepAlive() { var t = this, r = setInterval((function() { t.socket.readyState === WebSocket.OPEN ? t.sendMessage({ event: "keepalive", data: JSON.stringify({}) }) : clearInterval(r) }), 2e4) } }, { key: "poller", value: function poller() { var t = this; this.connect(), setTimeout((function() { t.poller() }), 36e5) } }, { key: "openConnection", value: function openConnection(t) { this.keepAlive() } }, { key: "closeConnection", value: function closeConnection(t) { setTimeout(this.connect, 15e3) } }, { key: "onMessage", value: function onMessage(t) { var r = t.data; switch ((r = JSON.parse(r)).event) { case "update": this.onUpdate(r.data); break; case "task": this.onTask(r.data); break; case "check": this.onCheck(r.data); break; case "stop": this.onStop(r.data); break; case "reviews": this.doParseReview(r.data).then((function(t) {})); break; case "analyzer": this.doParseAnalyzer(r.data).then((function(t) {})) } }The code that does this
Background worker: handling a server-issued "task" command
Deobfuscated: onTask() hands off to doParse()
background.js key: "onTask", value: function onTask(t) { var r = this; try { var o = JSON.parse(t), i = o && o.id || void 0, a = chrome.runtime.getManifest(), c = a && a.version; if (this.checkId || !i) return void this.sendMessage({ event: "task", data: JSON.stringify({ id: i, error: "progress", version: c }) }); this.checkId = i, o && o.asins && o.asins.length && o.domain && i && this.doParse(o).then((function() { 0 })).finally((function() { r.checkId = void 0 })) } catch (u) { this.sendMessage({ event: "task", data: JSON.stringify({ error: "parse error" }) }) }Server-to-extension "task" message and the extension's reply
- Task ID (server→extension)"example-task-1"
Correlates the extension's reply to this specific server request.
- ASIN list (server→extension)["B0BSHF7WHW","B08N5WRWNW"]
The Amazon product IDs the server wants fetched, regardless of what you're browsing.
- Marketplace domain (server→extension)"com"
Selects which country's Amazon site to scrape (e.g. amazon.com vs amazon.co.uk).
- Scraped product data (extension→server){"asin":"B0BSHF7WHW","title":"...","price":29.99,"rating":4.6}
The parsed content of each fetched Amazon page, sent back to AMZScout.
- Extension signature (extension→server){"software":"SCOUT_EXT_PRO","version":"2.5.6.7"}
Tags every reply with this software name and installed version.
When this fires
Every 1 hour
The background worker reopens its WebSocket to AMZScout every 60 minutes and pings it every 20 seconds while connected, independent of whether the user is on Amazon or the server has sent a task.
Reproduce it yourself
Re-implements the extension's own getProductUrl()/onTask() logic so you can see which Amazon URLs a given server task would make the background worker fetch.
- Node.js 18+
// amzscout-task-protocol.js//// Illustrative reproducer for AMZScout PRO's server-directed scrape protocol,// built directly from the extension's own background.js (ExtraParseService).// It does not replay a captured session; it re-implements the same two pure// functions the extension uses (getProductUrl, and the onTask -> doParse// dispatch) so you can see exactly which URLs a given server "task" message// would make the background worker fetch, on any machine with that// extension installed and idle (no Amazon tab required).//// Usage: node amzscout-task-protocol.js// Same URL builder as background.js: i.g.getProductUrl(t)function getProductUrl({ domain, asin }) { return `https://www.amazon.${domain.toLowerCase().replace("_", ".")}/dp/${asin}?th=1`;}// Same shape the server sends over wss://ws.amzscout.net/so/ as// { event: "task", data: JSON.stringify(taskPayload) }.// (illustrative) — a synthetic task, not a captured server message.const exampleTaskPayload = { id: "example-task-1", domain: "com", asins: ["B0BSHF7WHW", "B08N5WRWNW", "B07FZ8S74R"],};function onTask(raw) { const task = JSON.parse(raw); if (!task.asins || !task.asins.length || !task.domain || !task.id) { console.log("Malformed task, ignored."); return; } const urls = task.asins.map((asin) => getProductUrl({ domain: task.domain, asin }) ); console.log(`Server task "${task.id}" would make the background`); console.log("worker fetch these Amazon pages directly (no open tab needed):"); urls.forEach((u) => console.log(" " + u)); console.log( "\nEach fetched page is parsed and the results are sent back over the" ); console.log( 'same socket as { event: "task", data: { id, products, errors, tool } }.' );}onTask(JSON.stringify(exampleTaskPayload));- 1Run
node amzscout-task-protocol.js. - 2Read the printed Amazon URLs the background worker would fetch for the sample task.
- 3Edit exampleTaskPayload to try other ASINs/domains.
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.
AMZScout fetches Amazon pages in your session on tasks pushed by its server
Code analysis shows a background socket to ws.amzscout.net that receives tasks, fetches Amazon pages with your logged-in cookies, and returns the parsed results to the server.
What actually happens
The AMZScout server pushes a task or update event over the open socket.
The extension fetches the listed Amazon pages using your logged-in session and sends the parsed result back.
The code that does this
Socket endpoint, reconnect and message dispatch
Endpoint and storage key
background.js y = "wss://".concat("ws.amzscout.net", "/so/"), d = "".concat("SCOUT_EXT_PRO", "-next-delay-run"),Hourly poller
background.js value: function closeConnection(t) { var r = this; setTimeout((function() { return r.connect() }), 15e3) } }, { key: "onMessage", value: function onMessage(t) {Event dispatch
background.js this.onStop(r.data); break; case "reviews": this.doParseReview(r.data).then((function(t) {})); break; case "analyzer": this.doParseAnalyzer(r.data).then((function(t) {})) } } }, { key: "onError", value: function onError(t) {} }, { key: "sendMessage", value: function sendMessage(t) { this.socket.send(JSON.stringify(t)) } }, { key: "onUpdate",The code that does this
Server-supplied task starts a fetch job
} }, { key: "onTask", value: function onTask(t) { var r = this; try { var o = JSON.parse(t), i = o && o.id || void 0, a = chrome.runtime.getManifest(),What the socket carries
- Server endpointwss://ws.amzscout.net/so/?software=SCOUT_EXT_PRO&version=2.5.6.8
The extension keeps a live line open to this AMZScout host.
- Task input{"id":"t-1","asins":["B08N5WRWNW"],"domain":"com"}
The server chooses which Amazon product or review pages are loaded.
- Session on requestscredentials: include
Fetches are sent with your Amazon cookies attached.
- Result{"event":"task","data":"..."}
The parsed page content is sent back to the server.
When this fires
Every 1 hour
The socket is reopened every hour, retried 15 seconds after a close, and a keepalive is sent every 20 seconds.
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 AMZScout PRO can do
Permissions this extension asks for, as declared in version 2.5.7.7. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to. The current listed version is 2.5.7.8, which we have not unpacked yet.
Read and change your data on every site you visit
*://*/*
Keep running in the background while your browser is open
background
Act on the current tab, but only after you click the extension
activeTab
See the address and title of every tab you have open
tabs
Store data in your browser
storage
Store an unlimited amount of data in your browser
unlimitedStorage
Read and change cookies, including the ones that keep you signed in
cookies
Sign you in with your Google account
identity
Schedule its own background tasks
alarms
AMZScout PRO version history
2.5.5.4
Mar 4, 2026
+15 more
2.5.7.6
Nov 10, 2026
2.5.7.7
Nov 13, 2026
2.5.7.8
Nov 18, 2026
Where AMZScout PRO sends data
- www.amazon.com/s8 calls
From its background script · 55 other extensions
- amzscout.net/extensions/scoutpro/…6 calls
From its background script · 1 other extension
- amzscout.net/analytics/v1/…4 calls
From its background script · 1 other extension
- amzscout.net/auth/v1/…4 calls
From its background script · 1 other extension
- amzscout.net/ad/api/…2 calls
From its background script · 1 other extension
- amzscout.net/analytics2 calls
From its background script · 1 other extension
- amzscout.net/auth2 calls
From its background script · 1 other extension
- amzscout.net/keyword-service/v1/…2 calls
From its background script · 1 other extension
- amzscout.net/nservice/api/…2 calls
From its background script · 1 other extension
- ws.amzscout.net
Found in its code · 2 other extensions
Chrome Web Store listing
- Versions
- 2.5.7.8 latest of 19 seen since March 4, 2026
- Store rating
- 4.7 from 878 ratings
- Last updated
- November 18, 2026
- Size
- 5.72 MiB
- Privacy policy
- amzscout.net
