ClawHub
Back to skill

Security audit

Tmp.Jvf7zwyNjk

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward TripAdvisor MCP setup guide with expected API-key and package-install steps, though users should pin and review the external npm package before running it.

Before installing, review the referenced npm package or build from source, pin an exact version if possible, keep `.mcp.json` out of version control when it contains an API key, and use a dedicated revocable TripAdvisor Terra API key with quota limits.

A.I.G

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

Error
Location
SKILL.md:17
Finding

Unpinned Third-Party Package Is Automatically Downloaded and Executed

Content
View full analysis
Remediation
View remediation
"] ``` 2. Prefer an explicit installation step backed by a committed lockfile and npm integrity metadata instead of downloading code during each MCP launch. 3. Review the selected package version, its lifecycle scripts, and its transitive dependencies before deployment. 4. Use automated dependency monitoring and require a new security review before updating the pinned version. 5. Run the MCP server in a sandbox or container with: - A dedicated low-privilege account. - Read-only access to only the files it needs. - Restricted outbound network access. - No unnecessary home-directory or project-wide access. 6. Supply only `TRIPADVISOR_API_KEY` to the process rather than inheriting unrelated sensitive environment variables. 7. Store the API key through a protected secret-management mechanism where supported. If a configuration file must contain it, restrict file permissions and ensure `.mcp.json` is excluded from version control. 8. Use a dedicated, revocable, least-privilege API key with quota controls and monitor it for unexpected usage. ]]>

SkillSpector

Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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 (1)

MCP Config Access

High
Category
Agent Snooping
Confidence
95% confidence
Finding

Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.

Content

Scanner excerpt · SKILL.md (reported line 17)May include surrounding context.

Option A — npx (recommended)

Add to .mcp.json in your project or ~/.claude/mcp.json:

json
{

Static analysis

No suspicious patterns detected.