T08 · Insecure Dependencies
- Location
SKILL.md:9- Finding
Unpinned and Unaudited Package Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent local mock checkout demo, but its recommended installer runs mutable code outside the reviewed artifact and can change OpenClaw setup.
Install only from a trusted, reviewed AP2 checkout. Avoid running the one-command `npx -y` installer unless you are comfortable with it modifying OpenClaw and starting local services; prefer verifying the AP2 commit and pinning the `mcporter` version first.
SKILL.md:9Unpinned and Unaudited Package Execution
The skill is marked user-invocable and its description is broad enough to encourage autonomous checkout actions, but it does not clearly constrain when it may be invoked or what preconditions must be satisfied before initiating sensitive purchase flows. In a payment-related skill, ambiguous scope increases the chance of accidental activation, unsafe delegation, or use outside the intended mock/demo environment, especially since the document contains operational steps for approvals, mandates, and checkout completion.
The skill instructs users to run an install command via npx -y file:... install, which executes code from a local repository path without any integrity pinning, signature verification, or immutable version guarantee. In this context, the risk is elevated because the command is explicitly marketed as a one-command setup that also patches OpenClaw and starts backend services, so a tampered AP2 checkout or modified local repo could execute arbitrary code with the user's privileges.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The script prints a recommended install command using npx -y file:... install, which encourages execution of a package entrypoint without an explicit immutable version pin. If the referenced package path or surrounding repository state is changed unexpectedly, users may run altered installer code with their local privileges during setup.
The instruction requires explicit approval via fixed phrases 'yes / approve / 确认', which embeds a specific language/locale choice in the policy text. Because the file does not state that users may approve in their preferred language, this can conflict with language/locale flexibility requirements.