Is MaxAI: Ask AI anything as you browse (GPT, Gemini, Claude, Grok, etc.) safe?

High risk

MaxAI is high risk. Code analysis shows the extension passes the active tab address into each api.maxai.me request. In version 8.37.4 the encrypted header carries a random value, timestamp, signature and device ID, not the address.…

MaxAIv8.37.4Extension ID mhnlakgilnojmhinhkckjpncpbhabphiChrome Web Store
69Risk
Who publishes it

MaxAI - no other listings under this identity, 6 shared hostnames

Publisher
MaxAI

Shared hosts - 6 hostnames

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.

a16z.com
Also called by 4 other listings, including PM Gems – Product insights in every new tab, Dagur
api.maxai.me
Also called by 5 other listings, including WebChatGPT: ChatGPT with internet access, WebChatGPT
app.maxai.me
Also called by 5 other listings, including WebChatGPT: ChatGPT with internet access, WebChatGPT
maxai.co
Also called by 5 other listings, including WebChatGPT: ChatGPT with internet access, WebChatGPT, PrettyPrompt
maxai.me
Also called by 5 other listings, including WebChatGPT: ChatGPT with internet access, Chat to Notion
przyklad.com
Also called by 6 other listings
AI-assisted analysis.

MaxAI findings

MaxAI passes the active tab address into its api.maxai.me request pipeline

MediumunwantedCWE-359Static analysis

Code analysis shows the extension passes the active tab address into each api.maxai.me request.

What actually happens

You did this

You use a MaxAI feature that calls the MaxAI API.

The extension did this

The extension records the address of your active tab with the request and adds an encrypted X-Authorization header.

Whether the address leaves the device in that header was not observed.

The code that does this

Active tab address recorded as fromUrl, then header builder called

Readable version
background.js (deobfuscated, ~line 20190)
fromUrl: n.fromUrl || (typeof window < "u" ? window.location.href : "")
background.js (deobfuscated, ~line 20097)
let {  headers: n,  encryptData: r} = await Ih.getAPIEncryptHeaders(t.url, t, t.fromUrl);

The code that does this

Fields placed in the encrypted X-Authorization header in 8.37.4

Readable version
headers.set("X-Authorization", encrypt({  "X-Random": String(randomSixDigit),  "t": timestamp,  "p": signature,  "d": await getAPIFetchDeviceID()}, key))

What the encrypted header carries in code (8.37.4)

  • Device ID
    3f6c1a2e-8b47-4d0e-9a35-5c2d7e1b9f04

    A persistent random ID stored locally, sent on each call.

  • Timestamp
    1762905600123

    Server-adjusted time used for request signing.

  • Request signature
    a41f0c9e7b2d5638...

    SM3 hash of version, time and path.

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 MaxAI installed

  1. Open chrome://extensions and turn on Developer mode to show IDs. Find the one with ID mhnlakgilnojmhinhkckjpncpbhabphi and choose Remove.
  2. Scan your browser to check the rest of your extensions.

MaxAI version history

  1. 8.36.0

    Mar 4, 2026

  2. +1 more

  3. 8.37.3

    Aug 24, 2026

  4. 8.37.2

    Aug 24, 2026

  5. 8.37.4

    Nov 5, 2026

Chrome Web Store listing

Versions
8.37.4 latest of 5 seen since March 4, 2026
Store rating
4.6 from 14,496 ratings
Last updated
November 5, 2026
Size
30.92 MiB
Privacy policy
www.maxai.me
Updated July 21, 2026