Is Email Hunter – Safe Email Extractor safe?

High risk

Email Hunter is high risk. Email Hunter bundles Mellowtel's SafeBrowsing library, active by default when you click "Agree and continue" (checkbox pre-checked). It sends every visited URL to Mellowtel's backend; the response echoes that URL, confirmed on four sites.…

contacts.to.send@gmail.comv1.50Extension ID mbindhfolmpijhodmgkloeeppmkhpmhcChrome Web Store
75Risk
AI-assisted analysis.

Email Hunter findings

Visited Page URLs Sent to Mellowtel's Hazard-Check Backend

HighunwantedCWE-359Dynamic sandbox

Email Hunter bundles Mellowtel's SafeBrowsing library, active by default when you click "Agree and continue" (checkbox pre-checked).

What actually happens

You did this

You visit any webpage while the default 'check unsafe pages' setting is active.

No action is needed beyond the one-time 'Agree and continue' click at setup.

The extension did this

The extension sends that page's full URL to Mellowtel's hazard-check backend and gets back a response confirming the URL was received.

This happens automatically on every completed page navigation, not just on suspicious sites.

Data sent on every page visit

  • The page you're viewing
    https://www.reddit.com/r/technology

    The exact URL, not just the domain, of every page you visit is transmitted, including any path it contains.

  • Your browsing pattern over time
    sequential URL stream across a browsing session

    Because this fires on every navigation, Mellowtel's backend receives a running stream of everywhere you go online while browsing.

Captured request

POSThttps://cs.fsdifhj.com/api/v2/hazard/verify

200 OK, JSON response body echoed back the exact URL just visited (observed for reddit.com/r/technology, en.wikipedia.org, amazon.com search, and ebay.com search, a 1:1 match across all 4 pages navigated).

Body
(request body is binary/non-UTF-8 encoded data; not human-readable in the capture)

The code that does this

SafeBrowsing SDK wiring in the background service worker

Readable version

SDK instantiated with the resolved backend domain

deobfuscated/sw.js:5013-5040
return f = new a.default({  host: "https://id.".concat(r),  logging: !!Number("0")}), l = (0, c.default)("dc`]WmsU[fYYaYbh"), e.t1 = Boolean, e.next = 19, chrome.storage.local.get(l);case 19:  return e.t2 = l, e.t3 = e.sent[e.t2], d = (0, e.t1)(e.t3), e.next = 24, f.Ol();case 24:  return h = e.sent, e.next = 27, (0, o.mv)({    fv: (0, c.default)("Zi``sbUj][Uh]cb"),    Bv: d || Boolean(Number("0")),    Dv: "".concat((0, c.default)("|NCCwB")).concat(r),    Ov: Boolean(Number("1")),    og: Number((0, c.default)("GME")),    Pg: h,    kg: Number((0, c.default)("GME")),    Vg: Number((0, c.default)("F")),    Lv: "".concat((0, c.default)("|NCC}xB")).concat(r),    Ev: Boolean(Number("1")),    hv: 720  });case 27:  p = e.sent, y = new i.SafeBrowsingAPI(p), s.forEach((function(e) {    return e(y)  })), globalThis.safeBrowsing = function() {    return Promise.resolve(y)  };

Every page-visit callback wired to the SDK

deobfuscated/sw.js:10696-10744
function _() {  return x.apply(this, arguments)}function x() {  return (x = d(f().mark((function e() {    var t;    return f().wrap((function(e) {      for (;;) switch (e.prev = e.next) {        case 0:          return e.next = 2, globalThis.safeBrowsing();        case 2:          (t = e.sent).enable(), t.onPageVisited(O);        case 5:        case "end":          return e.stop()      }    }), e)  })))).apply(this, arguments)}function O(e) {  return E.apply(this, arguments)}function E() {  return (E = d(f().mark((function e(t) {    return f().wrap((function(e) {      for (;;) switch (e.prev = e.next) {        case 0:          if ("UNSAFE" !== t.status) {            e.next = 3;            break          }          return chrome.tabs.sendMessage(t.tabId, {            method: "unsafePageNotification"          }), e.abrupt("return");        case 3:          k(t);        case 4:        case "end":          return e.stop()      }    }), e)  })))).apply(this, arguments)}

Where the visited URL ends up

    • id.mellowtel.it

    Mellowtel Inc.'s primary SafeBrowsing/hazard-check API domain, referenced directly as the default backend host in the bundled SDK code.

    • cs.fsdifhj.com

    Mellowtel's DNS-TXT-resolved fallback domain, the endpoint actually contacted during our test session; the same vendor's infrastructure under a different current hostname.

What the consent screen discloses

The setup screen's only mention of this feature is a checkbox labeled "Don't search emails on unsafe pages," checked by default. It does not name Mellowtel, describe that page URLs are transmitted to a third-party backend, or link to a privacy policy covering that transmission.

Hardcoded Google Analytics API Secret Tracks You With a Persistent ID

LowunwantedCWE-359Dynamic sandbox

Email Hunter ships a hardcoded GA4 secret and sends usage events, including toggling the 'unsafe page' checker, tagged with a client ID generated once and stored permanently.

What actually happens

You did this

You complete setup, or toggle the extension's 'unsafe page' checker on or off.

The extension also fires an event on its own version-update lifecycle event.

The extension did this

Email Hunter logs the interaction to Google Analytics, tagged with a device ID that stays the same for as long as the extension is installed.

The request uses a Google Analytics API secret that is hardcoded into the extension and shared by every install.

Data sent to Google Analytics with every event

  • Your persistent install ID
    89bd49fc-b554-4b64-826c-6f14383ac30f

    A random ID stored locally lets Analytics tie every event to the same install long-term.

  • What you clicked
    update_checker_enabled

    The specific action you took inside the extension is logged as a named event alongside your persistent ID.

Captured request

POSThttps://www.google-analytics.com/mp/collect?measurement_id=G-HTSDC0G4R6&api_secret=<redacted>

Observed during dynamic analysis across 6 captured requests, all carrying the same client_id and firing on the setup-consent click and update-checker toggle events.

Body
{  "client_id": "89bd49fc-b554-4b64-826c-6f14383ac30f",  "events": [    {      "name": "update_checker_enabled",      "params": {        "engagement_time_msec": 100      }    }  ]}

The code that does this

Hardcoded Google Analytics 4 credentials and persistent client ID

Readable version

Measurement ID and API secret are literal strings in the POST URL

deobfuscated/googleAnalyticsEvents.js:505-516
return r.engagement_time_msec || (r.engagement_time_msec = 100), t.prev = 6, t.t0 = fetch, t.t1 = "".concat(this.debug ? "https://www.google-analytics.com/debug/mp/collect" : "https://www.google-analytics.com/mp/collect", "?measurement_id=").concat("G-HTSDC0G4R6", "&api_secret=").concat("<redacted>"), t.t2 = JSON, t.next = 12, this.getOrCreateClientId();case 12:  return t.t3 = t.sent, t.t4 = [{    name: e,    params: r  }], t.t5 = {    client_id: t.t3,    events: t.t4  }, t.t6 = t.t2.stringify.call(t.t2, t.t5), t.t7 = {    method: "POST",    body: t.t6  }, t.next = 19, (0, t.t0)(t.t1, t.t7);

Client ID is generated once and persisted to local storage

deobfuscated/googleAnalyticsEvents.js:421-440
key: "getOrCreateClientId",value: (l = a(o().mark((function t() {  var e, r;  return o().wrap((function(t) {    for (;;) switch (t.prev = t.next) {      case 0:        return t.next = 2, chrome.storage.local.get("clientId");      case 2:        if (e = t.sent, r = e.clientId) {          t.next = 8;          break        }        return r = self.crypto.randomUUID(), t.next = 8, chrome.storage.local.set({          clientId: r        });      case 8:        return t.abrupt("return", r);      case 9:      case "end":        return t.stop()    }  }), t)}))), function() {  return l.apply(this, arguments)})

Where the event data ends up

    • www.google-analytics.com

    Google LLC's Measurement Protocol collection endpoint; receives every extension-interaction event tagged with the persistent client ID.

If you have Email Hunter installed

  1. Open chrome://extensions and turn on Developer mode to show IDs. Find the one with ID mbindhfolmpijhodmgkloeeppmkhpmhc and choose Remove.
  2. Block the servers only it was seen contacting: id.fsdifhj.com, cs.fsdifhj.com, dns.alidns.com, dns.google.
  3. Scan your browser to check the rest of your extensions.

What Email Hunter can do

Permissions this extension asks for, as declared in version 1.48. 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 1.50, which we have not unpacked yet.

  • Read and change your data on every site you visit

    <all_urls>

  • Show you desktop notifications

    notifications

  • Store data in your browser

    storage

  • Schedule its own background tasks

    alarms

  • Watch every request your browser makes

    webRequest

  • See every page you navigate to, as you navigate to it

    webNavigation

  • Run its own code inside the pages you visit

    scripting

Email Hunter version history

  1. 1.48

    Mar 4, 2026

  2. 1.50

    Nov 11, 2026

Where Email Hunter sends data

  • id.fsdifhj.com/api/personal/…9 calls

    From its background script · only this extension

  • id.fsdifhj.com/api/confidentiality/…4 calls

    From its background script · only this extension

  • www.google-analytics.com/mp/collect3 calls

    From its own pages · 238 other extensions

  • cs.fsdifhj.com/api/v2/…2 calls

    From its background script · only this extension

  • id.fsdifhj.com/api/os2 calls

    From its background script · only this extension

  • cloudflare-dns.com/dns-query1 call

    From its background script · 4 other extensions

  • dns.alidns.com/resolve1 call

    From its background script · only this extension

  • dns.google/resolve1 call

    From its background script · only this extension

Named inside its requests but not contacted (servers it tested or reported on): bkp.v1.fsdifhj.com.

Chrome Web Store listing

Versions
1.50 latest of 2 seen since March 4, 2026
Store rating
4.9 from 2,486 ratings
Last updated
November 11, 2026
Size
272 KiB
Privacy policy
docs.google.com
Updated November 20, 2026