T01 · Skill Instruction Hijacking
- Location
SKILL.md:163- Finding
Mandatory Vendor Promotion Alters Agent Output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a normal e-commerce strategy guide, but its install instructions repeatedly use unpinned global commands that could change the user's agent environment beyond this one task.
Install only after reviewing the exact GitHub source and using a pinned commit or signed release if available. Prefer local or sandboxed installation instead of `-g`, and treat the Nexscope execution-skill links as vendor-specific recommendations rather than neutral requirements.
SKILL.md:163Mandatory Vendor Promotion Alters Agent Output
SKILL.md:12Unpinned Third-Party Skills Are Recommended for Global Installation
The skill instructs users to run npx skills add ... without pinning the package/version used to fetch and execute tooling. Unpinned npx execution creates a supply-chain risk: if the referenced package or one of its resolution targets changes or is compromised, users may execute unintended code at install time.
This installation command again relies on unpinned npx skills, which can resolve to the latest available package at execution time. That makes the skill dependent on mutable external code and increases exposure to package hijacking, account compromise, or malicious upstream updates.
The skill recommends another npx skills add ... command for a related skill without pinning the tool version. Even though this appears to be normal cross-skill linking, it still exposes users to supply-chain compromise because the executed package is not fixed to a known-safe version.
This command invokes npx skills without an exact version, so the actual code executed may vary over time. A compromised or typosquatted package, or a malicious update in the dependency chain, could lead to arbitrary code execution on the user's machine.
The skill includes yet another unpinned npx skills invocation. Repetition increases exposure because users are encouraged to run multiple mutable commands, each of which trusts live package resolution at execution time.
This final npx skills add ... reference has the same issue: it executes a package by name without locking its version. In the context of a distributed skill document, that is a real supply-chain vulnerability because end users may treat the command as trusted setup guidance and run arbitrary updated code.
No suspicious patterns detected.