Is MuteDeck safe?
MuteDeck sends supported meeting call state from meeting pages to a local WebSocket.
When you use supported meeting pages such as Google Meet, Zoom, Teams, StreamYard, Riverside, or Jitsi, MuteDeck content scripts read call status from the page and pass it to the background script. The background script JSON-serializes that status and sends it to the configured MuteDeck WebSocket, defaulting to ws://localhost:3492.
Who publishes itMartijn Smit - no other listings under this identity, 1 shared hostname
Martijn Smit - no other listings under this identity, 1 shared hostname
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 1 hostname
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.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed MuteDeck 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.
- ws://localhost:3492
MuteDeck sends data to ws://localhost:3492. Named as a recipient in this extension's own analysis.