T03 · Remote Payload Retrieval and Execution
- Location
references/setup.md:18- Finding
Unpinned Remote Package Execution and Persistent Global Installation
- Remediation
View remediation
... ``` 2. Publish and verify package integrity hashes or signed release provenance before execution. 3. Remove `-y` from recommended installation commands where interactive approval is possible. 4. Do not perform `npm i -g` as an implicit side effect. Make global CLI installation a separate, explicitly approved step. 5. Default to `--no-cli` and a project-local installation rather than modifying the global environment. 6. Display an exact configuration-change preview and require explicit user approval before editing each agent configuration file. 7. Back up existing configuration and apply narrowly scoped, atomic modifications. 8. Document the package's transitive dependencies and use lockfiles, provenance attestations, and automated dependency scanning. 9. Do not pass onboarding tokens on command lines, where they may appear in shell history or process listings. Use standard input, an OS credential prompt, or a protected temporary file. 10. Provide an uninstall procedure that removes the MCP registration, global command, cached credentials, and configuration changes. ]]>
