Back to skill

Security audit

Kubernetes Deployment Workflows

Security checks for vulnerabilities and agentic risk

Overview

This Kubernetes deployment helper needs review because its setup installs powerful, persistent cluster components without fully explaining their scope.

Review controller installation separately from application deployment. Confirm the target cluster, pin and inspect installation manifests, review cluster-wide permissions and monitoring scope, and agree on removal steps. The static scan reported no findings; the Review verdict rests on the setup's verified scope and disclosure gaps, without evidence of malicious intent.

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

Activation keywords include ordinary terms without requiring Kubernetes context.

Medium
Category
Trigger Abuse
Confidence
98% confidence
Finding

The skill activates when the user mentions words such as "update", "upgrade", "scale", or "release", which commonly occur in unrelated requests. Although the skill's overall subject is Kubernetes, these activation conditions do not explicitly require that context or exclude unrelated uses.

Content

No source excerpt is available for this finding.

Prerequisite installation instructions omit warnings about cluster-wide changes from remote manifests.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The prerequisite commands directly apply remotely retrieved installation resources without pinning an immutable version or requiring inspection and approval of cluster-wide changes. These controller installations can introduce CRDs and cluster-scoped RBAC; compromised upstream content or an unexpected upstream change could therefore affect the cluster within the executing identity's permissions. The official upstream repositories reduce suspicion of malicious intent, but the deployment-agent context makes these instructions operationally consequential.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.