The source intentionally relaunches a sandbox-born hub outside Seatbelt without a separate user confirmation, which is a meaningful isolation bypass even though it is limited to this hub’s startup path. The postinstall hook only sends an authenticated request to the local hub when a token is configured, so it does not show external data theft.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The hub starts on macOS with ZCODE_ACP_SANDBOX_ACTIVE set by a sandboxed backend spawn.
Impact
The hub runs without the Seatbelt restrictions inherited by the original process, reducing containment for remote session handling.
Mechanism
It writes a temporary LaunchAgent plist and uses launchctl to bootstrap and kickstart the hub outside the sandbox.
Evidence
dist/bin/hub.jsdist/remote/hub-sandbox.js${tmpdir()}/zcode-hub-relaunch-*/hub.plist${tmpdir()}/zcode-hub-relaunch-*/hub.log${tmpdir()}/zcode-hub-relaunch-last
Network endpoints1
127.0.0.1:${port}/api/upgrade