ClawHub
Back to skill

Security audit

Crypto payments for agents and humans, full stack with Payram

Security checks for vulnerabilities and agentic risk

Overview

This skill is payment-focused and mostly coherent, but it asks users or agents to run an unpinned external MCP server and use codebase-scanning/scaffolding tools for sensitive payment flows without enough scoping or safeguards.

Review before installing. Use this only when you explicitly intend to integrate PayRam, run the MCP server in a sandbox or disposable development environment, pin the referenced repository to a reviewed commit, avoid exposing unrelated secrets or wallet credentials, and use a clean branch before project assessment or scaffolding.

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

Unpinned Third-Party Repository and Dependency Execution

Content
View full analysis
Remediation
View remediation

SkillSpector

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill description is extremely broad and markets itself for many payment-related use cases, including high-risk and no-KYC contexts, which increases the chance an agent will invoke it for loosely related requests. Over-broad invocation language can cause unintended tool selection and expose users to risky payment-generation, deployment, or integration workflows without sufficiently explicit user intent.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill instructs users to assess a codebase and scaffold full applications, including payment creation, payouts, webhook handling, and a web console, but does not warn that these actions may read existing repositories and create or modify files. In an agentic setting, this can lead to unexpected repository changes, generated code insertion, or expansion of a sensitive payment-handling surface without explicit confirmation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.