Is Quick Search Tool safe?
Quick Search Tool is high risk. Every search through the built-in provider goes to query.quicksearchtool.com with an install ID, install date and fixed source ID added. Two searches shared the same ID, tying your search history together.
Quick Search Tool findings
Adds a permanent tracking ID to every search made with Quick Search Tool
Every search through the built-in provider goes to query.quicksearchtool.com with an install ID, install date and fixed source ID added.
Two searches shared the same ID, tying your search history together.
What actually happens
You type a search query into the address bar while Quick Search Tool is installed.
The extension appends your persistent UUID, install date, and source code to the search URL before it leaves your browser.
This happens on every search with no opt-out or disclosure in the extension UI.
Captured request
Tracking parameters appended to every search request
- Your persistent user ID1fda50f2-f581-da67-1737-7158dc72a231
A UUID assigned to your browser at install. Appears in every search request, linking all your searches, even across restarts.
- Install sourcenocache
A code indicating how the extension was acquired (e.g. which distribution partner referred you). The same value is sent with every search.
- Install date20260415
The date you installed the extension, as YYYYMMDD. Combined with the UUID, lets the server compute how long you've been a user.
- Traffic source / AP codeappfocus1
A campaign or traffic-source code set at install time. Used to attribute the install to a distribution partner.
- Extension version + verticalquicksearchtool_1.3
The extension's ID string and version number, identifying which build you are running.
- Chrome extension IDedpknbmdcbpmffcmfafkchpkeloemafh
Your browser's unique identifier for this extension installation.
The code that does this
declarativeNetRequest rule appending tracking parameters to every search (background.js:11-40)
// Reads the 4 tracking values stored in chrome.storage.sync at install time,// then registers a declarativeNetRequest redirect rule (id:1) that fires on// every main_frame navigation to query.quicksearchtool.com/s.//// The rule uses a queryTransform to ADD these params to every search URL:// source — install-source code (e.g. 'nocache', 'web_store')// uid — persistent UUID assigned at install (your identity token)// ap — traffic/campaign source code (e.g. 'appfocus1')// uc — install date as YYYYMMDD (e.g. '20260415')// i_id — extension vertical + version (e.g. 'quicksearchtool_1.3')// cid — Chrome extension ID (unique per browser install)//// setSearchUrl() is called once at install/update in the onInstalled listener,// so the rule is always active for the lifetime of the extension.const setSearchUrl = async () => { const { src: installSource, uid: persistentUUID, ap: trafficSource, uc: installDate } = await chrome.storage.sync.get(['src','uid','ap','uc']); await chrome.declarativeNetRequest.updateDynamicRules({ removeRuleIds: [1], // remove old rule first (idempotent) addRules: [{ id: 1, priority: 1, action: { type: 'redirect', redirect: { transform: { queryTransform: { addOrReplaceParams: [ { key: 'source', value: installSource || 'nocache' }, { key: 'uid', value: persistentUUID || '' }, // ← your identity { key: 'ap', value: trafficSource || 'nocache' }, { key: 'uc', value: installDate || '17000101' }, { key: 'i_id', value: 'quicksearchtool_' + extensionVersion }, { key: 'cid', value: chrome.runtime.id }, ] } } } }, condition: { urlFilter: 'query.quicksearchtool.com/s', resourceTypes: ['main_frame'] } }] });};What's stored on your device
Written to synced storage at install, read before every search. Via chrome.storage.sync, they follow you across signed-in devices.
- Location
- chrome.storage.sync (set at install, read on every search)
{ "ap": "appfocus1", "uc": "20260415", "src": "nocache", "uid": "1fda50f2-f581-da67-1737-7158dc72a231"}Where your search data is sent
- query.quicksearchtool.com
Receives every search query along with the persistent UID and attribution parameters. This is the overridden default search engine endpoint.
- log.quicksearchtool.com
Receives lifecycle events (install, update, sync) with the same uid and attribution parameters via the sendLog() function in background.js.
Reproduce it yourself
Run this in the Chrome DevTools console (on any page) while Quick Search Tool is installed. It reads the tracking values from chrome.storage.sync and reconstructs the exact URL that will be used for your next search, so you can see your persistent UID and confirm it matches what gets sent.
- Chrome with Quick Search Tool installed
- DevTools access (F12)
// qst-tracking-checker.js// Run in Chrome DevTools console while Quick Search Tool is installed.// Reads the stored tracking values and shows the URL your next search will use.(async () => { const data = await chrome.storage.sync.get(['src', 'uid', 'ap', 'uc']); console.log('Stored tracking values:', data); const extensionVersion = chrome.runtime.getManifest().version; const extensionId = chrome.runtime.id; const testQuery = 'hello world'; const url = new URL('https://query.quicksearchtool.com/s'); url.searchParams.set('query', testQuery); url.searchParams.set('source', data.src || 'nocache'); url.searchParams.set('uid', data.uid || ''); url.searchParams.set('ap', data.ap || 'nocache'); url.searchParams.set('uc', data.uc || '17000101'); url.searchParams.set('i_id', 'quicksearchtool_' + extensionVersion); url.searchParams.set('cid', extensionId); console.log('Your next search URL (with tracking):'); console.log(url.toString()); console.log(''); console.log('Your persistent UID:', data.uid); console.log('This UID will appear in every search request from this browser.');})();- 1Install Quick Search Tool.
- 2Open a tab, press F12 for DevTools, switch to Console.
- 3Paste this script, press Enter; it prints your stored UID and the URL your next search will use.
- 4Search and compare the UID shown; they'll match.
If you have Quick Search Tool installed
- Open
chrome://extensionsand turn on Developer mode to show IDs. Find the one with IDkeadechokmcohlcampccppbjjeabghcdand choose Remove. - Scan your browser to check the rest of your extensions.
What Quick Search Tool can do
Permissions this extension asks for, as declared in version 1.3. 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 quicksearchtool.com
*://*.quicksearchtool.com/*
Read and change your data on query.quicksearchtool.com
*://query.quicksearchtool.com/*
See the address and title of every tab you have open
tabs
Store data in your browser
storage
Block and redirect the requests your browser makes
declarativeNetRequest
Read and change cookies, including the ones that keep you signed in
cookies
Chrome Web Store listing
- Versions
- 1.3 seen since March 4, 2026
- Store rating
- 5.0 from 2 ratings
- Last updated
- April 2, 2024
- Size
- 11.19 KiB
- Privacy policy
- search.quicksearchtool.com
