Is Bee Hive safe?
BeeHive is medium risk. When you use the Bee Hive new-tab search, the extension submits it to search.beehivetab.com with extra fields added to the URL: search context plus stored values including a persistent user UUID, install token, and affiliate click ID.…
Who publishes itextbeehive - no other listings under this identity
extbeehive - no other listings under this identity
What this publisher told the store about itself, and the other listings that told it the same thing.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Findings
New-tab searches send query URLs with persistent identifiers.
When you use the Bee Hive new-tab search, the extension submits it to search.beehivetab.com with extra fields added to the URL: search context plus stored values including a persistent user UUID, install token, and affiliate click ID.
What actually happens
The user submits a search from the extension's new-tab page.
The extension submits the search request with stored user and affiliate identifiers appended as form fields.
Captured request
Fields in the request
- Your search URLhttps://search.beehivetab.com/?q=weather (illustrative)
The request carries the search URL context submitted from the new-tab page.
- Stored extension identifiersuserId=d7f3a1b2-...&utm_uid=affiliate-click-id (illustrative)
Values from storage that link searches to one installation: a persistent user UUID, install token, affiliate click ID, and install timing.
Install beacon sends a generated user ID to the extension's vendor
On first install, the worker generates a random UUID and POSTs it to beehivetab.com with your browser name and two identifier values.
Dynamic analysis observed the real UUID sent.
The code reads the response for an auth token and click ID.
What actually happens
The user installs the Bee Hive extension for the first time.
The extension generates a random installation ID and sends it, along with the browser name and two fixed identifiers, to the vendor's server in a POST request.
This happens automatically on install, before any other interaction with the extension.
Captured request
The server returned an error status during this test session, so no response payload was captured.
{ "uid": "a51c97d2-ba8b-4a45-9c15-33def9803b1b", "b": "chrome", "extension": "BeeHiveTabCh", "theme_index": 7}Fields in the install request
- Generated installation IDa51c97d2-ba8b-4a45-9c15-33def9803b1b
A random UUID created at install, sent to the vendor and reused on later requests to link them to this installation.
- Browser namechrome
Identifies which browser the extension is running in.
- Extension identifierBeeHiveTabCh
A fixed, vendor-assigned label for this build and distribution channel.
- Theme index7
A fixed numeric code identifying the install variant.
What this test session did and didn't capture
The install request itself, including the generated UUID, was captured in full during dynamic analysis. The vendor's server returned an error status in this session, so we could not directly observe what it sends back. The extension's source code shows it reads the response body for an authentication token and an affiliate click ID, then writes both to local storage next to the installation UUID.
What it can do
Permissions this extension asks for, as declared in version 4.0.9. 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 beehivetab.com
*://beehivetab.com/*
Store data in your browser
storage
Read and change your bookmarks
bookmarks