Back to skill

Security audit

sher

Security checks for vulnerabilities and agentic risk

Overview

This skill does what it claims by deploying frontend previews, but users should treat the npm install and public preview upload as real security considerations.

Before installing, confirm you trust the shersh npm package and prefer a pinned, reviewed version or an isolated environment. Only deploy projects whose built output can be shared through an externally accessible preview URL, and review build artifacts for secrets or private content first.

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:17
Finding

Unpinned Third-Party npm Package Installation and Execution

Content
View full analysis
Remediation
View remediation
link ``` 2. Avoid recommending global installation. Use a project-local development dependency with a committed lockfile: ```bash npm install --save-dev --save-exact shersh@ ``` 3. Commit and review `package-lock.json`, and use `npm ci` in controlled environments to enforce locked dependency resolution. 4. Verify package provenance, expected publisher identity, registry source, and integrity metadata before execution. 5. Review package lifecycle scripts and dependency changes when upgrading. Where operationally feasible, disable lifecycle scripts during installation and explicitly invoke only reviewed functionality. 6. Run the deployment tool in an isolated, least-privilege environment with restricted filesystem, credential, and network access. 7. Document the trusted package version and an upgrade-review process so future releases are not executed automatically without reassessment. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill instructs users to deploy frontend projects to a public preview URL but does not clearly warn that build artifacts are uploaded to a third-party service and may expose embedded secrets, proprietary assets, internal endpoints, or unpublished content. In an agent context, this omission is more dangerous because the agent may deploy automatically on the user's behalf without adequately surfacing the data-transfer and exposure risk.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
96% confidence
Finding

The skill recommends executing an unpinned package via npx shersh, which fetches and runs the latest published code at execution time. If the package is compromised, typo-squatted, or a malicious update is published, the agent could execute attacker-controlled code in its environment with access to project files, credentials, and build outputs.

Content

No source excerpt is available for this finding.