The flagged shell, network, and command-output behavior is tied to the package’s stated remote coding terminal: the CLI connects to its own service, and local actions are performed as server-directed job steps within connected workspaces. The manifest has no install lifecycle hooks, and the reviewed paths show no unrelated collection or persistence.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
When the user starts the CLI and connects a session, or requests work through the service.
Impact
The service can direct local coding actions within the product workflow; no unrelated collection, install-time behavior, or persistence was identified.
Mechanism
The CLI sends session context to the CompletionPrism service; server-directed coding actions run through the local executor, which restricts workspace operations to connected folders and can use an OS sandbox.
Evidence
out/cli-start.jsout/machine/line/index.jsout/machine/executor/shell.jsout/machine/executor/sandbox.js
Network endpoints2
completionprism.illuminis.ai/api/v1/front-door/terminal/live