Is Firefish Sourcing Extension safe?

Clean risk

Firefish Sourcing Extension embeds a shared OAuth client secret and sends it during Firefish token exchanges.

The extension uses a built-in Firefish OAuth client ID and client secret when exchanging authorization codes or refreshing tokens. It posts those OAuth credentials to Firefish's API and then stores returned access and refresh tokens locally in the browser.

storeadminv1.0.33Chrome Web Store
0Risk

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

What it can do

Permissions this extension asks for, as declared in version 1.0.33. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Store data in your browser

    storage

  • Sign you in with your Google account

    identity

  • See the address and title of every tab you have open

    tabs

  • Start, monitor and manage your downloads

    downloads

  • Add items to the right-click menu

    contextMenus

Where it sends data

Destinations our analysis observed Firefish Sourcing Extension contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.

  • api.firefishsoftware.com

    Firefish Sourcing Extension sends data to api.firefishsoftware.com. No other extension we have analysed sends data here.

Updated 21 September 2026gnnnbgkmbljmjghbhjhbfiiffndpnjij