The reviewed network and credential flows are tied to the user-started Orbit login and connector, with the device token sent to the Orbit service it belongs to. The flagged process execution and filesystem activity support the bridge’s documented operation; no malicious automatic behavior was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs the orbit CLI, normally orbit login, and confirms device authorization through Orbit.
Impact
The intended bridge carries Orbit feature requests to the local app and Codex session; no unrelated credential collection or hidden install-time activity was identified.
Mechanism
The CLI saves the issued Orbit device token and opens a relay connection to the selected Orbit server; relay requests are limited to the local Orbit API.
Evidence
~/.config/orbit/device.json~/.config/orbit/runtime/
Network endpoints3
orbit.cubesugar.techwss://orbit.cubesugar.tech/agentUser-selected HTTPS Orbit server and its derived WSS /agent endpoint