ClawHub
Back to skill

Security audit

inventory-replenishment-ledger

Security checks for vulnerabilities and agentic risk

Overview

This skill is a small inventory-planning helper whose disclosed behavior matches its stated purpose, with only minor routing ambiguity.

Installers should understand that this skill may be selected for inventory planning requests and can call a recording stage when asked to record a quantity; use clear prompts with explicit quantities or inventory fields.

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

Vague Triggers

Medium
Confidence
92% confidence
Finding
The activation language is broad enough that an agent could match this skill for general 'inventory planning work' rather than only narrowly scoped replenishment tasks. That can cause unintended tool invocation or inappropriate routing, especially in multi-skill environments where loose matching increases the chance of acting on partially related requests.

Vague Triggers

Medium
Confidence
86% confidence
Finding
The instruction to 'invoke the stage requested by the user' is ambiguous because it does not define how to distinguish between selection versus recording requests, nor what prerequisites must be satisfied before recording. In practice, this can let an agent invoke the wrong stage or skip validation of whether the needed inputs were explicitly supplied by the user.

Static analysis

No suspicious patterns detected.