The flagged configuration writes are gated behind explicit installation commands, while the credential client sends its token to the configured Primitive service. The reviewed startup and broker paths did not show unrelated collection or concealed remote code execution.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
CLI commands and registered hooks; agent and Cursor configuration writes require explicit install commands.
Impact
The inspected behavior supports Primitive’s decision capture, agent integration, and authenticated service requests; no unrelated credential transfer or concealed remote execution was found.
Mechanism
The client sends credentials to the configured Primitive API, and the machine broker runs the package’s own daemon entry point. Reviewed agent configuration changes are command-driven.
Evidence
package.jsondist/index.jsdist/chunk-JFWJN2ME.jsdist/chunk-L32WYFJT.jsdist/chunk-ZKXNJB6U.jsdist/chunk-NJBN3WXF.js