The reported credential and data-transfer signals resolve to local credential-presence checks and Firebase’s anonymous authentication for the Bridge’s push-notification feature. Persistence is reachable only through the user-invoked setup command, and no malicious behavior was found on install or import.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Firebase authentication occurs when the server starts; launchd or systemd persistence is created only when the user runs the setup command.
Impact
No unauthorized credential or application-data transfer was identified. User-invoked setup makes the Bridge start as a service.
Mechanism
The server creates or refreshes an anonymous Firebase session for push notifications. The doctor connectivity check posts an empty body to Firebase. The setup command writes the service configuration and registers it with the platform service manager.
Evidence
~/.ccpocket/firebase-credentials.json~/Library/LaunchAgents/com.ccpocket.bridge.plist
Network endpoints2
identitytoolkit.googleapis.comsecuretoken.googleapis.com