Is Huntr - Job Search Tracker & Autofill safe?
Huntr is medium risk.
Track job applications and autofill online application forms from your Huntr profile.
This extension lets you save job opportunities from websites and record details such as posting URLs, titles, salaries, locations, companies, notes, tasks, dates, contacts, and events. It also supports one-click application autofill on many job and ATS sites using information from your Huntr profile, with saved opportunities available in a dashboard and kanban board.
Who publishes itHuntr LLC - no other listings under this identity
Huntr LLC - no other listings under this identity
Huntr findings
Huntr sends user ID and page URLs to Mixpanel over unencrypted HTTP
Code analysis shows tracking events carrying your user ID and, for some events, page addresses go to api.mixpanel.com over plain HTTP, so anyone on the network path could read them.
What actually happens
You sign in, save a job, or autofill an application form.
Install, update, logout and upgrade clicks also fire events.
The extension sends a tracking event to api.mixpanel.com over unencrypted HTTP.
The event carries your user ID, and for some events the page URL.
Fields in the base64 data parameter per source code.
- distinct_iddistinct_id (user ID, set after login)
The Huntr user ID that ties each event to one account.
- pageUrl / hostpageUrl and host of the current job page
The address of the page involved, sent with job-added and autofill events.
- token1d6f823f8d5432354b55fc0af879343c
The vendor project token that routes events to its Mixpanel project.
- version2.0.45
The installed extension version.
The code that does this
Tracker built on an http:// origin
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.
Save Job uploads page URL and job-page content
Using Huntr's Save Job action sends the page URL, scraped job description, title, company, location, and parsing metadata to https://huntr.co/api/job.
DA didn't observe the POST, as no session or save action was performed.
What actually happens
You click Save Job while viewing a job listing.
The extension sends the job page URL and scraped job content to Huntr's job API.
Fields built into the saved-job request
- Current job page URLhttps://jobs.example.com/software-engineer-remote-12345
This identifies the listing page you saved.
- Scraped job description<div class="description">Build browser automation tools for recruiting teams.</div>
This contains job-page content collected from the page, such as the description HTML or text.
- Job titleSenior Software Engineer
This records the job title shown on the page you saved.
- CompanyExample Robotics
This records the company associated with the saved listing.
- Parsing metadatadomParsingData: { source: "json-ld", confidence: 0.94 }
This can include page-derived details used to structure the saved job entry.
Captured request
Not observed during unauthenticated dynamic analysis; the shipped save-job path constructs this POST.
- Content-Type
- application/json
- Authorization
- Bearer <redacted>
The code that does this
Save Job maps page-derived fields into a Huntr API POST
Readable equivalent of the saved-job API method
background.bundle.jsaddJob(company, listId, jobTitle, htmlDescription, location, url, domParsingData) { if (!token || !userId) return Promise.reject(); const body = JSON.stringify({ company, listId, jobTitle, htmlDescription, location, url, domParsingData, isFromChromeExtension: true, }); return apiRequest(`/job?id=${userId}`, "POST", body);}Readable equivalent of the Save Job handler
background.bundle.jsSAVE_JOB(message) { const { company, listId, jobTitle, htmlDescription, location, postUrl, _sender } = message; return function (respond) { mixpanel.track("103 Chrome Ext Job Added", { url: postUrl }); respond({ type: "SAVING_JOB", tabId: _sender.tab.id }); api.addJob(company, listId, jobTitle, htmlDescription, location, postUrl) .then(function (result) { respond({ type: "RECEIVE_SAVED_JOB", job: result.job, company: result.company, list: result.list, tabId: _sender.tab.id, }); }) .catch(function (error) { return respond(apiError(error, "add_job", _sender.tab.id)); }); };}Readable equivalent of the content-script Save button
content.bundle.jsfunction JobFound({ parsedJob, onJobSaved, currentBoard, organization }) { const location = { address: parsedJob.address || "" }; const jobTitle = parsedJob.title || ""; const postUrl = window.location.href; const htmlDescription = parsedJob.description || ""; function save(company) { if (!company.name) return; if (location && location.address) { getTopPlaceSuggestion(location.address).then(function (place) { return onJobSaved(company, jobTitle || "No Job Title", htmlDescription, place || location, postUrl); }); } else { onJobSaved(company, jobTitle || "No Job Title", htmlDescription, location, postUrl); } } return renderSaveButton(save, currentBoard, organization);}Destination in this claim
- huntr.co
Huntr API host receiving saved-job records from the extension.
Extension sends your email and name to Mixpanel over unencrypted HTTP
Your email and first name are sent to Mixpanel in plain text, so anyone on the network could read them.
What actually happens
You log in to Huntr through the extension.
The extension sends a Mixpanel profile update with your email address, first name, and user ID.
Fields built into the Mixpanel profile update
- Your account emailalex.rivera@example.com
This directly identifies the Huntr account used in the extension.
- Your first nameAlex
This adds a personal name to the profile record sent after login.
- Your Huntr user ID64f1c2a73b8e4d0012a9c456
This ties the profile update to the same account identifier used by the extension.
- Chrome-use flaghasChrome: true
This marks the profile as using the Chrome extension.
Why you can't catch this in DevTools
The profile JSON is base64-encoded before being placed in the URL query string.
{ "$token": "1d6f823f8d5432354b55fc0af879343c", "$distinct_id": "64f1c2a73b8e4d0012a9c456", "$set": { "$first_name": "Alex", "$email": "alex.rivera@example.com", "hasChrome": true }}Captured request
Not observed during unauthenticated dynamic analysis; the shipped login path constructs this GET request.
The code that does this
Login calls the profile update, which sends the HTTP Mixpanel request
Readable equivalent of the shipped login/profile logic
background.bundle.jsconst MP_API_URL = "http://api.mixpanel.com/";const MIXPANEL_TOKEN = "1d6f823f8d5432354b55fc0af879343c";let distinctId = null;const manifest = chrome.runtime.getManifest();const mixpanel = { track(eventName, properties) { properties = properties || {}; const event = { event: eventName, properties: Object.assign({ token: MIXPANEL_TOKEN, version: manifest.version }, properties), }; if (distinctId) event.properties.distinct_id = distinctId; const data = btoa(JSON.stringify(event)); return fetch(`${MP_API_URL}track/?data=${data}`); }, updateUser(email, givenName) { if (distinctId) { const profile = { $token: MIXPANEL_TOKEN, $distinct_id: distinctId, $set: { $first_name: givenName, $email: email, hasChrome: true, }, }; const data = btoa(JSON.stringify(profile)); return fetch(`${MP_API_URL}engage/?data=${data}`); } }, setDistinctId(userId) { distinctId = userId; }, clearDistinctId() { distinctId = null; },};const auth = { login(token, userId, user) { chrome.storage.local.set({ token, userId }, function () { Uo.setTokenAndId(token, userId); mixpanel.setDistinctId(userId); mixpanel.updateUser(user.email, user.givenName); }); },};Destination in this claim
- api.mixpanel.com
Mixpanel profile endpoint receiving the base64-encoded profile update over HTTP.
+1 more finding not shown
What Huntr can do
Permissions this extension asks for, as declared in version 2.0.44. 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.0.45, which we have not unpacked yet.
Read and change your data on every site you visit
http://*/*
Read and change your data on every secure site you visit
https://*/*
Read and change your data on ajax.googleapis.com
https://ajax.googleapis.com/
Read and change your data on app.huntr.co
https://app.huntr.co/
Read and change your data on localhost:3000
http://localhost:3000/*
Read and change your data on huntr.co
https://huntr.co/*
Read and change your data on huntrstaging.com
https://huntrstaging.com/*
Read and change your data on fonts.googleapis.com
https://fonts.googleapis.com/css?family=Lato:300,400,700,900
Schedule its own background tasks
alarms
Store data in your browser
storage
See the address and title of every tab you have open
tabs
See every page you navigate to, as you navigate to it
webNavigation
Run its own code inside the pages you visit
scripting
Store an unlimited amount of data in your browser
unlimitedStorage
Where Huntr sends data
- Huntr
Named in our analysis · only this extension
Chrome Web Store listing
- Versions
- 2.0.44 seen since March 4, 2026
- Store rating
- 4.8 from 1,319 ratings
- Last updated
- April 27, 2026
- Size
- 1.24 MiB
- Privacy policy
- huntr.co
