The package’s sandboxed hub startup deliberately relaunches the hub outside Seatbelt through launchd, crossing a security boundary automatically when that startup path is reached. The behavior is tied to the remote hub’s terminal feature and is not clearly malicious, but the isolation bypass is a meaningful risk.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The hub starts with the sandbox birth marker inherited from a sandboxed backend spawn.
Impact
The hub operates beyond the sandbox boundary, weakening isolation for subsequent remote session handling and terminal launches.
Mechanism
The hub writes a temporary LaunchAgent plist and uses launchctl to bootstrap and kickstart a hub process outside the sandbox, passing selected environment values.
Evidence
dist/bin/hub.jsdist/remote/hub-sandbox.jspackage.jsondist/remote/hub-upgrade-notify.jsdist/quota/client.js<system temporary directory>/zcode-hub-relaunch-*