The reviewed behavior matches the package’s bridge and push-notification purpose. Credential checks do not expose credential values, and service persistence is user-invoked; no malicious behavior was identified.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Firebase anonymous authentication starts with the bridge server; doctor checks run via the doctor command or endpoint; launch-agent persistence requires the setup command.
Impact
No evidence that third-party credentials or unrelated host, user, or project data are sent to an external collector, or that persistence is installed without a user command.
Mechanism
The doctor checks credential-file existence and probes Firebase with an empty body. Push relay requests use a Firebase anonymous token. Launch-agent setup writes the service plist only when invoked through the setup command.
Network endpoints3
identitytoolkit.googleapis.comsecuretoken.googleapis.comus-central1-ccpocket-ca33b.cloudfunctions.net