Is INSSIST | Web Client for Instagram safe?

Medium risk

INSSIST is medium risk. Code analysis shows that if the remote config includes a search term, the extension queries Instagram's music search and posts track details to api.inssist.com without the user acting.…

inssist.comv41.0.5Extension ID bcocdbombenodlegijagbhdjbifpiijpChrome Web Store
52Risk
Who publishes it

Slashed - no other listings under this identity, 5 shared hostnames

Publisher
inssist.com
Declared legal entity
Slashed
Registered address
Ankerstrasse 10, Zurich 8050, CH
Registered contact
Hanna Laas

Shared hosts - 5 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.

api.inssist.com
Also called by 3 other listings, including Opalite for Instagram | AI Web Client
fc.inssist.com
Also called by 3 other listings, including Opalite for Instagram | AI Web Client
inssist.com
Also called by 3 other listings
storage.inssist.com
Also called by 3 other listings, including Opalite for Instagram | AI Web Client
tunetank.com
Also called by 3 other listings, including Opalite for Instagram | AI Web Client
AI-assisted analysis.

INSSIST findings

Remote config can make extension post Instagram music results to inssist.com

MediumunwantedCWE-829Static analysis

Code analysis shows that if the remote config includes a search term, the extension queries Instagram's music search and posts track details to api.inssist.com without the user acting.

What actually happens

You did this

The remote config response includes a music search query.

Code analysis shows the config response is inspected for an mscr property.

The extension did this

The extension searches Instagram music and posts track records to api.inssist.com.

Per the code, the search uses the signed-in Instagram session.

The code that does this

Readable version
Send the collected track list to the extension's own API at /mscr/tracks.

Fields in each uploaded track record (values illustrative)

  • Track id
    1234567890

    Instagram identifier of a music track.

  • Artist
    Example Artist

    Performer name from Instagram's search result.

  • Track name
    Example Track

    Title of the track.

  • Cover image
    (base64 jpeg, 76x76)

    Small cover image encoded as a base64 JPEG.

Hosts involved in the music search flow

    • api.inssist.com

    Receives the posted track records and issues the config that triggers the search.

    • i.instagram.com

    Instagram endpoint queried for music search results.

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.

Browsing Instagram Clips forwards music track details to api.inssist.com

MediumunwantedCWE-200Static analysis

Code analysis shows that while the Clips feed loads, the extension reads music details from Instagram's responses and forwards them to api.inssist.com.

What actually happens

You did this

You open the Instagram Clips home feed.

Code analysis shows a rule matching POST /graphql/query responses that contain the clips home connection.

The extension did this

The extension extracts music fields from each item and posts them to api.inssist.com.

The code forwards the edges to the background through a clipsFeed event.

The code that does this

Readable version
When a graphql response contains the Clips home edges, pass those edges to the background as a clipsFeed event.

Track fields read from the feed (values illustrative)

  • Audio cluster id
    1234567890

    Instagram identifier for the track.

  • Title
    Example Track

    Track title shown on the clip.

  • Display artist
    Example Artist

    Artist name shown on the clip.

  • Cover thumbnail
    https://scontent.cdninstagram.com/example.jpg

    Cover image URL fetched and resized before upload.

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.

Extension fetches remote config every six hours and reloads itself to apply it

LowunwantedCWE-829Static analysis

Code analysis shows the extension fetches config from api.inssist.com every six hours, merges it into its settings, and reloads itself, so behavior can change without a store update.

What actually happens

You did this

The extension asks api.inssist.com for settings on a timer.

Code analysis shows an alarm named fusion.refresh-config firing every six hours and once at startup.

The extension did this

The returned settings are merged in and the extension reloads.

Per the code, the reload is skipped only when the popup is open.

The code that does this

Readable version
Every six hours, and immediately on startup, call checkNewVersion() to fetch the remote config.

The code that does this

Readable version
If the response contains a config object, deep-merge it over the current config, save it, then reload the extension.

Request and the settings it can alter

  • Config endpoint
    api.inssist.com/api/v1/fusion?version=41.0.1

    Where the settings are fetched from.

  • Version parameter
    41.0.1

    Tells the server which build is asking.

  • Feature flags
    boost.enableBoost

    Settings the server can change, such as boost and avatar options.

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.

What INSSIST can do

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

  • Read and change your data on instagram.com

    *://*.instagram.com/*

  • Read and change your data on inssist.com

    *://*.inssist.com/*

  • Schedule its own background tasks

    alarms

  • Keep running in the background while your browser is open

    background

  • Read and change cookies, including the ones that keep you signed in

    cookies

  • Block and redirect the requests your browser makes

    declarativeNetRequest

  • Run hidden pages in the background

    offscreen

  • Store an unlimited amount of data in your browser

    unlimitedStorage

INSSIST version history

  1. 35.3.6

    Mar 4, 2026

  2. +45 more

  3. 41.0.3

    Nov 14, 2026

  4. 41.0.4

    Nov 16, 2026

  5. 41.0.5

    Nov 16, 2026

Where INSSIST sends data

  • api.inssist.com/api/v1/…9 calls

    From its background script · only this extension

  • www.instagram.com4 calls

    From its background script · 24 other extensions

  • fonts.googleapis.com/css2 calls

    From a script it injects into websites · 384 other extensions

  • fonts.googleapis.com/css22 calls

    From a script it injects into websites · 384 other extensions

Chrome Web Store listing

Versions
41.0.5 latest of 49 seen since March 4, 2026
Store rating
4.7 from 8,076 ratings
Last updated
August 11, 2026
Size
9.65 MiB
Privacy policy
inssist.com
Updated July 21, 2026