ClawHub
Back to skill

Security audit

Kubernetes Networking

Security checks for vulnerabilities and agentic risk

Overview

Review is advised because a network-blocking example could disrupt applications across the default namespace without clear safeguards.

Start in a test namespace with restricted Kubernetes permissions. Before allowing changes, confirm the target cluster, namespace, affected applications, and exact manifests. For isolation policies, establish required application and DNS allowances, verify connectivity, and prepare a rollback before applying them to production.

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
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • 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
Findings (2)

The namespace-wide deny-all policy is applied without warning about connectivity loss.

High
Category
Output Handling
Confidence
98% confidence
Finding

The executable example applies an ingress-and-egress deny-all policy to every pod in the default namespace without a connectivity warning or a staged rollout. Where network-policy enforcement is active, pods without other applicable allow policies can lose application traffic, DNS access, and dependency connectivity, causing an outage. Default-deny isolation is a legitimate security technique, and this is an example rather than an unconditional execution directive, but its broad scope and missing safeguards make accidental application dangerous.

Content

No source excerpt is available for this finding.

Activation keywords include everyday terms without an explicit Kubernetes-context requirement.

Medium
Category
Trigger Abuse
Confidence
97% confidence
Finding

The activation list includes standalone terms such as "service", "traffic", and "port", which commonly occur outside Kubernetes networking. Although the skill's description identifies its domain, these explicit invocation conditions do not require Kubernetes context or exclude unrelated uses.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.