The sandbox relaunch crosses a security boundary when the hub starts with the sandbox marker, creating a concrete persistence and sandbox-bypass risk that warrants a warning. The inspected install-time notifier targets the configured local hub and does not establish credential theft or an unrelated installation beacon.
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 on macOS with the inherited marker showing that it was born inside the Seatbelt sandbox.
Impact
The hub runs beyond the sandbox restrictions. The inspected plist does not configure automatic loading or keep-alive, and the source does not show an unrelated credential recipient.
Mechanism
The hub writes a temporary LaunchAgent plist and uses launchctl to bootstrap and start itself in the user’s GUI domain outside the sandbox.
Evidence
dist/remote/hub-sandbox.jsdist/bin/hub.jspackage.jsondist/remote/hub-upgrade-notify.jsdist/handlers/account.jsdist/quota/live.jsdist/remote/hub-server.js