Is TrustPlugin safe?
TrustPlugin relays cryptographic signing requests from any web page to a native PKI host without validating the message origin.
The extension injects a content script on every page that listens for postMessage events from any origin and forwards them to a background script, which routes them to the native host chrome.trust.plugin via native messaging. The native host exposes operations including signature generation, encryption, decryption, and certificate management. On macOS the same operations are sent over an unencrypted WebSocket to ws://localhost:9000, where any local process can observe or inject frames.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itSergey Trust - no other listings under this identity, 2 shared hostnames
Sergey Trust - 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.
Where it sends data
Destinations our analysis observed TrustPlugin 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.
- chrome.trust.plugin
TrustPlugin sends data to chrome.trust.plugin. No other extension we have analysed sends data here.
- localhost:9000
TrustPlugin sends data to localhost:9000. Named as a recipient in this extension's own analysis.