The conditional launchd relaunch intentionally moves the hub outside its inherited Seatbelt sandbox without asking the user in this code path, creating a meaningful sandbox-bypass risk. The inspected code ties this behavior to the hub's terminal feature and does not show unrelated payload execution, so the evidence supports a warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
The hub starts with the sandbox birth marker inherited from a sandboxed backend.
Impact
This bypasses the hub process's sandbox restrictions and runs it with the user's ordinary process access; the inspected code does not establish broader malicious activity.
Mechanism
It writes a temporary LaunchAgent plist and uses launchctl bootstrap and kickstart to run the hub outside the sandbox. The plist does not enable RunAtLoad or KeepAlive.
Evidence
dist/bin/hub.jsdist/remote/hub-sandbox.js<system-temp>/zcode-hub-relaunch-*/hub.plist<system-temp>/zcode-hub-relaunch-last