T03 · Remote Payload Retrieval and Execution
- Location
scripts/script.sh:77- Finding
Unverified Remote Installer Piped Directly to Bash
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Helm helper is mostly coherent, but it needs Review because it can affect live Kubernetes releases, including rollbacks, while its top-level description understates that authority.
Review this before installing if you use Helm against real clusters. Treat list/status/values/history/diff as cluster-reading commands and rollback as production-impacting. Use a least-privilege kubeconfig and namespace, avoid running rollback through automation unless you have separately confirmed the target cluster and revision, and do not follow the printed curl-to-bash Helm install command without independent verification.
scripts/script.sh:77Unverified Remote Installer Piped Directly to Bash
The description presents the skill as a local Helm chart utility, but the documented commands also interact with live clusters and repositories, including listing releases, reading deployed state, and performing rollbacks. This mismatch can mislead users into approving or invoking the skill without understanding that it can affect real environments and external registries.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Commands
### `KUBECONFIG`
Path to kubeconfig file
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Commands
### `KUBECONFIG`
Path to kubeconfig file
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Commands
### `KUBECONFIG`
Path to kubeconfig file
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Commands
### `KUBECONFIG`
Path to kubeconfig file
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Commands
### `KUBECONFIG`
Path to kubeconfig file
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Commands
### `KUBECONFIG`
Path to kubeconfig file
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Commands
### `KUBECONFIG`
Path to kubeconfig file
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Commands
### `KUBECONFIG`
Path to kubeconfig file
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
KUBECONFIGPath to kubeconfig file
scripts/script.sh KUBECONFIG
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
### `KUBECONFIG`
Path to kubeconfig file
```bash
scripts/script.sh KUBECONFIG
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
### `KUBECONFIG`
Path to kubeconfig file
```bash
scripts/script.sh KUBECONFIG
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
### `KUBECONFIG`
Path to kubeconfig file
```bash
scripts/script.sh KUBECONFIG
Rollback is a cluster-changing, potentially production-impacting operation that is not justified by the stated purpose of chart scaffolding, linting, templating, or packaging. In this context, the capability is especially dangerous because it can alter live release state and trigger service disruption or rollback to insecure or broken revisions.
The skill exposes shell-backed operational capabilities but does not declare any tool scope such as permissions or allowed-tools. This makes the effective execution surface opaque to users and policy systems, increasing the risk of unintended command execution or broader-than-expected access.
The manifest description omits repository-management and cluster-management functions that are materially more sensitive than local chart scaffolding. In security-sensitive environments, incomplete disclosure reduces informed consent and can bypass user expectations or governance controls.
Several commands can modify local files, Helm repository configuration, or cluster-related state, but the skill does not warn users about these side effects. Lack of warnings is dangerous because users may treat the skill as informational when some operations are administrative or destructive.
The script exposes live cluster-management commands such as list, status, history, rollback, and manifest retrieval even though the skill description is focused on chart creation, linting, templating, and packaging. This scope expansion increases operational risk because a user invoking a seemingly chart-focused helper can unexpectedly interact with production clusters and release state.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
echo ""
echo " Or via package manager:"
echo " macOS: brew install helm"
echo " Snap: sudo snap install helm --classic"
echo " Chocolatey: choco install kubernetes-helm"
echo " apt (Debian): sudo apt-get install helm"
echo ""
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
echo ""
echo " Or via package manager:"
echo " macOS: brew install helm"
echo " Snap: sudo snap install helm --classic"
echo " Chocolatey: choco install kubernetes-helm"
echo " apt (Debian): sudo apt-get install helm"
echo ""
The rollback path executes a state-changing Helm rollback immediately after collecting or receiving a revision, but it does not require a final confirmation acknowledging the target cluster and consequences. This makes accidental destructive actions more likely, especially in automation or when the user assumes the helper is primarily read-only/chart-local.
The script includes repository mutation and remote search features not declared in the manifest description, which broadens network and configuration side effects beyond what a user would reasonably expect from a chart scaffolding/linting helper. While less severe than rollback, undeclared remote operations still weaken trust boundaries and increase attack surface.
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
_error "helm is not installed or not in PATH."
echo ""
echo "Install Helm v3:"
echo " curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash"
echo ""
echo " Or via package manager:"
echo " macOS: brew install helm"