ClawHub
Back to skill

Security audit

Stripe Best Practices

Security checks for vulnerabilities and agentic risk

Overview

This is a knowledge-only Stripe best-practices skill with no executable code, persistence, or hidden data access.

Installers should treat this as general Stripe integration guidance, not as authorization to handle live payment data or make account changes. For non-Stripe billing questions, users may want a more narrowly scoped skill or explicit instructions to avoid applying Stripe-specific recommendations automatically.

A.I.G

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

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 (1)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The listed intents such as 'integrate payment processing' and 'handle subscriptions' are high-level, generic requests without explicit scope boundaries or negative examples. In a markdown skill description, this can create ambiguous activation conditions and increase the chance of unintended invocation for general payments or subscription questions.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.