The flagged behavior is consistent with a machine-side task runner: it uses its own machine token with the configured Navarch API, while the QA fixture uses a generated token over loopback. No install-time data collection or unrelated credential destination was identified.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
CLI commands such as register or supervise, and QA fixture creation when called by a consumer.
Impact
No unrelated credential transfer or harmful default action was found in the reviewed paths.
Mechanism
The runtime sends its own machine credential to the configured Navarch control plane; the QA fixture creates a random token and sends it only to a loopback server.
Evidence
dist/qa-fixture.cjsdist/api.cjsdist/cli.cjs
Network endpoints2
localhost:3000 (configurable control plane)127.0.0.1 (ephemeral QA fixture server)