The package’s network and process behavior implements its disclosed Orbit connector: a user starts device login, confirms the computer, and runs a local bridge to the paired account. I found no install-time collection, unrelated credential transfer, or automatic execution of the CLI.
Static reason
One or more suspicious static signals were detected.
Trigger
The user runs `orbit login`, completes Orbit account and device confirmation, then keeps the CLI running.
Impact
The paired Orbit account can use the connector to view local Codex sessions and invoke the documented controls. The access is disclosed and requires device authorization and pairing.
Mechanism
The CLI saves a dedicated device credential, serves the local app on loopback, and opens an outbound relay connection that forwards requests to the local API and WebSocket.
Evidence
cli.mjsorbitrelay-agent.mjsserver.mjslib/rpc.mjs<ORBIT_HOME>/device.json or ~/.config/orbit/device.json<dataDir>/pairing-key
Network endpoints2
orbit.cubesugar.tech (default HTTPS service and WSS relay host)