The inspected credential flow obtains a dedicated device token through Orbit’s authorization process and sends it to that same configured Orbit service. Network access, local process execution, and background operation support the package’s stated remote connector function and are triggered through CLI commands.
Static reason
One or more suspicious static signals were detected.
Trigger
Explicit CLI use, normally orbit login followed by starting the connector.
Impact
The Orbit service can relay requests and responses for the connected computer, consistent with the package’s remote-access purpose; no unrelated credential collection or unsolicited account action was found.
Mechanism
The CLI obtains device authorization from the configured Orbit server, saves the issued device token, and the relay agent authenticates to that server’s relay while forwarding permitted API requests to loopback.
Evidence
device.jsonpairing-keyconnector.logconnector.lockservice.json
Network endpoints3
orbit.cubesugar.techConfigured Orbit server HTTPS endpoint