The package's default behavior starts only when the user runs its CLI and completes Orbit device authorization. Its relay and process execution support the documented bridge, and the reviewed paths showed no unrelated credential exfiltration or hidden startup behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs the orbit CLI and completes Orbit's device authorization; the connector then runs in the background by default.
Impact
Orbit can provide the documented remote access to the user's selected computer and sessions.
Mechanism
The connector authenticates to Orbit using its device token and relays Orbit API traffic to the local service. The reviewed code showed no unrelated credential collection or destination.
Evidence
cli.mjslib/connector-service.mjsrelay-agent.mjsserver.mjslib/rpc.mjs
Network endpoints2
orbit.cubesugar.techORBIT_RELAY_URL (configurable)