Is Everykey for Chrome safe?
Everykey for Chrome forwards website-supplied desktop-app commands from all sites to the local Everykey app.
The extension runs a content script on every website and relays page messages into its background service worker. That worker sends the command body to the local Everykey desktop app over a WebSocket, allowing website-supplied messages to request vault and passkey operations such as reading, creating, and updating vault objects.
Who publishes itEverykey Inc. - no other listings under this identity, 1 shared hostname
Everykey Inc. - 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.
What it can do
Permissions this extension asks for, as declared in version 5.4.3. 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
Run its own code inside the pages you visit
scripting
See the address and title of every tab you have open
tabs
Where it sends data
Destinations our analysis observed Everykey for Chrome 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.
- localhost:35727
Everykey for Chrome sends data to localhost:35727. Named as a recipient by 1 other extensions we have analyzed.