Is Frame Companion safe?
Frame Companion forwards page JSON-RPC wallet requests and page origin to the local Frame desktop wallet.
Frame Companion injects a wallet provider into file, HTTP, and HTTPS pages, then relays page-origin JSON-RPC requests through the extension. The background script adds the page origin to each payload and sends it to the local Frame desktop wallet over a WebSocket connection.
Who publishes itFrame Labs - no other listings under this identity, 2 shared hostnames
Frame Labs - no other listings under this identity, 2 shared hostnames
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 2 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.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 0.12.1. 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 secure site you visit
https://*/*
Read and change your data on every site you visit
http://*/*
Act on the current tab, but only after you click the extension
activeTab
Schedule its own background tasks
alarms
Detect when you step away from your computer
idle
Run its own code inside the pages you visit
scripting
Where it sends data
Destinations our analysis observed Frame Companion 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.
- 127.0.0.1:1248
Frame Companion sends data to 127.0.0.1:1248. No other extension we have analysed sends data here.