Package supply-chain risk

Dependency Script Execution

Install scripts, postinstall hooks, and package-manager credentials can create dangerous paths when agents modify dependencies or run commands.

Severity: HighDetected by: Pro

Signals CapitalGuard looks for

Postinstall, prepare, or prepublish scripts

Package registry tokens in config files

Agent-accessible dependency update automation

Package scripts can run code during routine install or build steps.

Agent-suggested dependency changes can trigger scripts outside normal review attention.

Registry credentials can expose private packages or publish permissions.

Require review for dependency and lifecycle-script changes.

Move package registry credentials out of the repo workspace.

Run dependency updates in isolated environments with limited secrets.

Next step

Related threats

Agent instruction risk

Hidden instructions in docs, issues, prompts, logs, and internal notes can influence coding agents when those files become task context.

AI tools do not need to print raw keys to create risk; file paths, variable names, logs, and configuration context can reveal how systems are wired.

Some files should not be read, edited, summarized, or sent to external tools by autonomous coding agents.