Is Nickel Pass safe?
Nickel Pass is high risk. It counts visits and active time per site you browse, then uploads the list with your profile email to admin.nicklpass.com every 3 minutes. Observed during dynamic analysis.…
Who publishes itnicklpass - no other listings under this identity
nicklpass - no other listings under this identity
Nickel Pass findings
NICKLpass uploads per-site visits and active time with your profile email
It counts visits and active time per site you browse, then uploads the list with your profile email to admin.nicklpass.com every 3 minutes.
Observed during dynamic analysis.
What actually happens
You keep normal web pages open in the focused window.
The background worker adds visit and active-time counts for each domain every second.
When this fires
Every 3 minutes
Per-domain totals are posted to admin.nicklpass.com every 180 seconds.
Fields in the upload body
- Domainexample.com
The site hostname you had active.
- Active time184
How long that site was in the active tab.
- Visits3
Number of visits counted that day.
- Profile emailuser@example.com
Sent on the fallback endpoint when no sign-in token exists.
The code that does this
Tracker poll and sync request
Focused-tab poll
const win = await chrome.windows.getLastFocused({populate: true});Upload
fetch('https://admin.nicklpass.com' + path, {method:'POST', headers:{'Content-Type':'application/json'}, body: JSON.stringify({email, activities})})Where the data goes
- admin.nicklpass.com
Receives per-domain activity, with a bearer token or the profile email.
NICKLpass uploads up to 5000 past history entries as per-domain visits once
Code analysis shows it reads up to 5000 past history entries once and uploads per-domain visits and time with your Chrome profile email.
Not confirmed in testing.
What actually happens
You sign in or the extension starts after update.
The worker reads past browsing history and uploads per-domain totals once.
The code that does this
History read
const items = await chrome.history.search({text:'', startTime, endTime, maxResults: 5000});Fields built from history
- Domainexample.com
Hostname of each past history entry.
- Visit dates2026-10-30
Per-day dates when you visited the site.
- Profile emailuser@example.com
Attached on the unauthenticated endpoints.
Where the data goes
- admin.nicklpass.com
batch_sync, anonymous_sync or managed_anonymous_sync endpoints receive the totals.
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.
If you have Nickel Pass installed
- Open
chrome://extensionsand turn on Developer mode to show IDs. Find the one with IDedcoecjbckgpokngfflempgihpnhadoaand choose Remove. - Block the servers only it was seen contacting:
admin.nicklpass.com. - Scan your browser to check the rest of your extensions.
Nickel Pass version history
5.6.9.2
Apr 11, 2026
+10 more
5.7.1.9
Oct 27, 2026
5.7.1.10
Nov 12, 2026
5.7.1.11
Nov 18, 2026
Where Nickel Pass sends data
- admin.nicklpass.com/api/v1/…4 calls
From its background script · only this extension
- admin.nicklpass.com/oauth/token2 calls
From its background script · only this extension
- us.i.posthog.com/e2 calls
From its background script · 28 other extensions
- fonts.googleapis.com/css1 call
From its own pages · 384 other extensions
- fonts.googleapis.com/css21 call
From its own pages · 384 other extensions
- fonts.gstatic.com/s/dmsans/…1 call
From its own pages · 323 other extensions
Chrome Web Store listing
- Versions
- 5.7.1.11 latest of 14 seen since April 11, 2026
- Store rating
- 2.9 from 14 ratings
- Last updated
- August 11, 2026
- Size
- 548 KiB
- Privacy policy
- www.nicklpass.com
