The flagged persistence is behind an explicit service-setup command, and the Firebase key/token flow supports the package’s stated push-relay function. The source reviewed shows no automatic install-time exfiltration or unrelated credential use.
Static reason
One or more suspicious static signals were detected.
Trigger
Firebase auth and relay activity occur when the Bridge server starts; launchd persistence requires the user to run `ccpocket-bridge setup`.
Impact
The package retains its own Firebase refresh token for push service continuity. No unrelated credential collection or hidden persistence was identified.
Mechanism
The Bridge creates or restores an anonymous Firebase identity for push notifications and sends its token to the ccpocket relay. Explicit setup writes a launch agent that runs the Bridge at login.
Evidence
~/.ccpocket/firebase-credentials.json~/Library/LaunchAgents/com.ccpocket.bridge.plist/tmp/ccpocket-bridge.log/tmp/ccpocket-bridge.err
Network endpoints3
identitytoolkit.googleapis.comsecuretoken.googleapis.com