Back to skill

Security audit

Warehouse Optimization

Security checks for vulnerabilities and agentic risk

Overview

The skill is a straightforward warehouse-advice guide, but its install command runs unpinned remote software and installs globally, which users should review before use.

Review or replace the install command before installing: prefer a pinned CLI version, an immutable commit or release for the skill source, and a non-global install where possible. The advisory content itself appears purpose-aligned, but do not treat its benchmark figures as a substitute for current platform fee schedules or business-critical verification.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:14
Finding

Unpinned npm CLI and Mutable Repository Installation

Content
View full analysis
Remediation
View remediation
add ... ``` 2. Pin repository content to a verified commit SHA or immutable signed release rather than using only the mutable owner/repository reference. 3. Publish and verify cryptographic checksums or signatures for the expected Skill package before installation. 4. Avoid global installation unless it is operationally required. Prefer a project-local or otherwise isolated installation to limit persistence and impact. 5. Use a lockfile or controlled internal package registry where the installation workflow supports it. 6. Document the expected package publisher, repository URL, version, commit hash, and verification procedure so users can detect dependency substitution. 7. Run installation in a least-privilege environment without administrative rights, production credentials, or unnecessary filesystem access. 8. Periodically review and update pinned versions through a controlled dependency-update process rather than allowing implicit upgrades during installation. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Ae4

Medium
Category
analysis-evasion
Confidence
80% confidence
Finding

Suspicious Unicode normalization or mixed-script content

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
93% confidence
Finding

The installation command uses npx skills add ... without pinning an exact package/version, which can cause users to fetch and execute whatever version is current at install time. If the upstream package, dependency chain, or registry account is compromised, users could run unreviewed code on their systems during installation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.