ClawHub
Back to skill

Security audit

Kubernetes Skills

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Kubernetes Velero backup and restore guide, with operational risks that users should control but no hidden or unrelated behavior found.

Install only if you expect the agent to help with Kubernetes Velero operations. Before allowing restore or schedule commands, confirm the active kube context, target namespaces, backup contents, retention policy, and whether Secrets or persistent-volume-related resources are included.

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

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The skill documents restore operations that can modify live Kubernetes resources, including namespace remapping and selective restoration of secrets/configmaps, but provides no warning, pre-flight validation, or guidance to confirm target cluster and namespace safety. In an agent-executed context, this omission increases the chance of accidental destructive changes, overwrites, or unintended recovery into production environments.

Missing User Warnings

Low
Confidence
80% confidence
Finding
The scheduled backup example creates an ongoing recurring backup policy without warning about retention, storage growth, backup destination costs, or the handling of potentially sensitive cluster data. While not directly destructive, this can lead to uncontrolled accumulation of backups, increased exposure of stored data, and operational impact if adopted blindly by an automated agent or inexperienced operator.

Static analysis

No suspicious patterns detected.