Is DataHive safe?

Medium risk

DataHive is medium risk.

DataHive runs server-supplied jobs in your browser that open pages and send their content back to its servers.

The extension's service worker polls api.datahive.ai for YAML workflows that open background tabs and off-screen iframes, then extract full page HTML, text, links and XPath-selected content and POST it back to DataHive. On x.com and twitter.com it captures your outgoing x-csrf-token request header and stores it, so server-supplied jobs can substitute it into fetch requests issued with your logged-in session and the extension's all-sites access. Every request to its backend also carries a device fingerprint (CPU model, OS, user-agent, persistent device ID and a bot-detection verdict).

DataHivev0.2.8Extension ID bonfdkhbkkdoipfojcnimjagphdnfedbChrome Web Store
49Risk
Who publishes it

Alcorn Labs OÜ - no other listings under this identity

Publisher
DataHive
Declared legal entity
Alcorn Labs OÜ
Registered address
Narva mnt 7-652, Kesklinna linnaosa, Tallinn, Harjumaa 10117, EE
Registered contact
Kos C.
AI-assisted analysis.

DataHive findings

DataHive saves your X CSRF token for remote job templates to insert

HighunwantedCWE-522Static analysis

Code analysis shows the extension saves the x-csrf-token header from your X and Twitter requests.

What actually happens

You did this

You browse x.com or twitter.com.

Any outgoing request to those hosts matches the extension's capture rule.

The extension did this

It saves your x-csrf-token header, which remote job steps can later insert into requests.

The saved value sits in extension storage until a job template references it.

The code that does this

Hardcoded capture rule and placeholder resolver, as shipped

Readable version
// Header capture rule{ urlsPatterns: ['*://x.com/*', '*://twitter.com/*'],  requestHeaders: [{ name: 'x-csrf-token', storageKey: 'twitterCsrfToken' }] }
// {{capturedData.twitterCsrfToken}} in a job step url/headers/body// is replaced with the stored value before fetch() runsconst value = await getCapturedData(key);if (value !== null) text = text.replace(token, value);

What is captured and where it goes

  • X CSRF token
    capturedData.twitterCsrfToken

    A request-signing value tied to your logged-in X session, saved in extension storage.

  • Job endpoint
    api.datahive.ai/api/job

    Where the extension polls for job steps that can reference the saved token.

Observation

Dynamic analysis was inconclusive. The test token was rejected by the vendor's API and no real X session was present, so no capture or replay was observed.

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.

DataHive version history

  1. 0.2.5

    Mar 4, 2026

  2. 0.2.8

    Sep 25, 2026

  3. 0.2.6

    Sep 25, 2026

Where DataHive sends data

  • fonts.googleapis.com/css23 calls

    From its own pages · 384 other extensions

  • fonts.gstatic.com/s/inter/…3 calls

    From its own pages · 323 other extensions

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

    From its own pages · 240 other extensions

  • m1.openfpcdn.io

    Found in its code · 1 other extension

  • api.datahive.ai

    Found in its code · only this extension

Chrome Web Store listing

Versions
0.2.6 latest of 3 seen since March 4, 2026
Store rating
4.3 from 26 ratings
Last updated
April 20, 2026
Size
1.03 MiB
Privacy policy
datahive.xyz
Updated July 21, 2026