Is Noise Cancelling App safe?

High risk

Noise Cancelling App is high risk. The extension adds a virtual mic, "Background Noise Remover." Picking it for mic access generates (or reuses) a UUID in cookie TSVB_UID, sent to effectssdk.ai to start a session, a stable ID reused across sessions, confirmed by capture.…

AI Webcam Effectsv1.5.7Chrome Web Store
69Risk
Who publishes it

DAMIKO INC - 8 other listings from the same operator, none carrying a finding

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
AI Webcam Effects
Declared legal entity
DAMIKO INC
Registered address
1833 S OCEAN DR 1403, HALLANDALE BEACH, FL 33009, US
Registered contact
DANIL KORSKY

Same store account

8 other listings published from this account, 65k+ users between them, none of them carrying a finding.

ai-webcam-effects-+-recor30k+MediumRemote Desktop20k+CleanLookGood Live5k+HighAudio Recorder: Free & Unlimited Recordings4k+CleanAI Noise Cancellation For Listeners3k+CleanCamera Picture In Picture (PIP Overlay)2k+Clean2 more listings in the relationship graph, on paid plans →

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

Publishers can request a review.

Findings

Persistent tracking ID sent to effectssdk.ai when virtual mic is used

MediumunwantedCWE-359Dynamic sandbox

The extension adds a virtual mic, "Background Noise Remover." Picking it for mic access generates (or reuses) a UUID in cookie TSVB_UID, sent to effectssdk.ai to start a session, a stable ID reused across sessions, confirmed by capture.

What actually happens

You did this

You select the extension's 'Background Noise Remover' virtual microphone on a site that requests audio.

For example, opening a meeting or mic-test page and choosing the virtual device in the browser's microphone picker.

The extension did this

The extension sends a persistent per-user ID from the TSVB_UID cookie to effectssdk.ai to open a processing session.

The same UUID is reused on later sessions, so it serves as a stable identifier for your use of the feature.

Captured request

POSThttps://effectssdk.ai/sdk/session/ac9445cb76d793fe92580ca06a99e33e29212575

HTTP 200. Captured during dynamic analysis after selecting the 'Background Noise Remover' virtual microphone. The user_id value equals the browser's TSVB_UID cookie.

Headers
Content-Type
application/json
Body
{  "user_id": "66c3ba98-234d-42ab-9131-06f423c7036f",  "payload": "eyJpdiI6..."}

Fields in the POST body

  • Your tracking ID (user_id)
    66c3ba98-234d-42ab-9131-06f423c7036f

    A UUID stored in the TSVB_UID cookie and reused on every session, making it a persistent identifier tied to your use of the virtual mic.

  • Session payload
    eyJpdiI6...

    An encoded payload used to authenticate and configure the SDK audio session.

  • Customer ID (in URL)
    ac9445cb76d793fe92580ca06a99e33e29212575

    Identifies which effectssdk.ai customer account the session belongs to. The same value is hardcoded in the extension.

The code that does this

How the persistent UID is created and stored (src/user_id.ts)

Readable version
// src/user_id.tsclass UserID {  getUID() {    let uid = Cookies.get('TSVB_UID');   // read existing cookie    if (!uid) {      uid = uuidv4();                    // first use: generate a UUID      Cookies.set('TSVB_UID', uid);      // persist it across sessions    }    return uid;                          // same value reused each session  }}

Where the identifier is sent

    • effectssdk.ai

    Cloud backend for the EffectsSDK noise-cancellation service; receives the persistent TSVB_UID (as user_id) and a session payload to open an audio-processing session.

Updated 30 September 2026njmhcidcdbaannpafjdljminaigdgolj