The extension has a solid user base of 200,000 users and maintains a good rating of 4.5 stars from 212 reviews, suggesting general user satisfaction. The name "WebRTC Control" clearly indicates its purpose of managing WebRTC settings, which aligns with the privacy permission usage. However, the lack of visible developer information reduces transparency and accountability.
The combination of privacy permission with broad content script injection across all websites creates significant security exposure. While privacy permission is necessary for WebRTC control, the universal content script access means the extension can read and modify any webpage you visit, potentially capturing sensitive information like passwords, personal data, or financial details. The storage permission, while common, allows data persistence that could be misused. The contextMenus permission is relatively benign but adds to the overall permission footprint.
Consider running this extension in a separate Chrome profile dedicated to privacy-focused browsing to limit exposure of your main browsing data. Before installation, verify the extension's source and check recent reviews for any security concerns. Monitor your browser's performance and network activity after installation. If you only need WebRTC control occasionally, consider using browser flags or temporary solutions instead of a persistent extension. Regularly review the extension's permissions and remove it if you notice any suspicious behavior or if your WebRTC control needs change.
| https://webbrowsertools.com/test-webrtc-leak/ | https://clients2.google.com/service/update2/crx | |
| https://mybrowseraddon.com/webrtc-control.html |
{ "name": "WebRTC Control", "icons": { "16": "data/icons/16.png", "32": "data/icons/32.png", "48": "data/icons/48.png", "64": "data/icons/64.png", "128": "data/icons/128.png" }, "action": { "default_icon": { "16": "data/icons/16.png", "32": "data/icons/32.png", "48": "data/icons/48.png", "64": "data/icons/64.png" }, "default_title": "WebRTC Control" }, "version": "0.3.4", "commands": { "_execute_action": {} }, "background": { "service_worker": "background.js" }, "options_ui": { "page": "data/options/options.html", "open_in_tab": true }, "update_url": "https://clients2.google.com/service/update2/crx", "description": "Have control over WebRTC (disable | enable) and protect your IP address.", "permissions": [ "privacy", "storage", "contextMenus" ], "homepage_url": "https://mybrowseraddon.com/webrtc-control.html", "content_scripts": [ { "js": [ "data/content_script/inject.js" ], "run_at": "document_start", "matches": [ "*://*/*" ], "all_frames": true } ], "manifest_version": 3, "web_accessible_resources": [ { "matches": [ "*://*/*" ], "resources": [ "data/content_script/page_context/media_devices.js", "data/content_script/page_context/support_detection.js", "data/content_script/page_context/additional_objects.js" ] } ] }
ⓘ CRXaminer has partnered with our friends at Secure Annex to provide additional findings unique to their platform.
Secure Annex also analyzes extensions from other browsers, IDEs, and can continuously monitor.
This extension may not yet be analyzed by Secure Annex.