T03 · Remote Payload Retrieval and Execution
- Location
references/command-library.md:69- Finding
Unverified Remote Shell Scripts Are Downloaded and Executed Directly
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for legitimate HAP upgrade guidance, but it may tell administrators to run unverified remote scripts on production infrastructure.
Review generated upgrade guides carefully before use. Do not run the included remote script one-liners on production hosts or Kubernetes control nodes unless you first download the script, verify its integrity from a trusted source, inspect it, and run it with the minimum required privileges. Replace placeholder/default passwords and avoid putting real credentials directly in shell history or shared runbooks.
references/command-library.md:69Unverified Remote Shell Scripts Are Downloaded and Executed Directly
The skill metadata and content are written exclusively in Chinese and the description strongly implies this skill should be used whenever HAP upgrade topics arise, without accommodating the user's preferred language. This can degrade user comprehension, increase the chance of operational mistakes during sensitive upgrade procedures, and reduce the user's ability to verify safety-critical instructions.
The template instructs operators to execute a shell script fetched directly from the network via curl and pipe it into bash, which removes any opportunity to inspect, verify, or pin the content before execution. In an upgrade skill, this is especially dangerous because users are likely to run it on privileged control nodes, so a compromised hosting endpoint, MITM, or replaced script could lead to immediate remote code execution and cluster compromise.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
The guide instructs operators to execute a script fetched directly from the network via curl ... | bash, which creates a classic remote code execution and supply-chain risk. In an upgrade skill, this is especially dangerous because users are likely to run the command on production servers with elevated privileges, making compromise of the hosting endpoint, DNS, TLS trust, or distribution path highly impactful.
The document normalizes passing database credentials directly on the command line (-p123456), which can expose secrets through shell history, process listings, screenshots, copied logs, and operational habits. In a production upgrade context, encouraging plaintext examples increases the chance that administrators reuse insecure invocation patterns with real credentials on sensitive systems.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
The command pipes a remotely fetched script directly into bash, causing immediate execution of network-delivered code without prior integrity verification, review, or a user-facing warning. In an upgrade skill, users are likely to run commands with elevated privileges on production systems, so a compromised host, CDN, DNS path, or publishing pipeline could lead to full server compromise or destructive changes.
This cluster variant has the same unsafe pattern: a remote script is fetched and executed immediately in a Kubernetes-related context, where compromise can affect multiple services or nodes. Because the skill is specifically for private-deployment upgrades, operators may treat these commands as authoritative and run them on sensitive infrastructure, amplifying the blast radius of any upstream or man-in-the-middle compromise.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
The template includes sed -i commands that perform in-place modification of deployment YAML and update scripts, which can irreversibly alter production configuration if run against the wrong path or with unexpected file contents. Although intended as a legitimate upgrade step, the lack of a strong warning, backup instruction, or validation step increases the risk of accidental service misconfiguration or outage.
All user-facing instructions are presented only in Chinese, and the file does not indicate that the language is optional, user-selected, or limited to a justified region-specific context. Under the stated policy, forcing a specific language without opt-in can be a natural-language policy violation.
The entire skill guidance is written in Chinese and does not indicate any option to use another language or locale. Under the stated policy, a skill that effectively enforces a specific language without opt-in can be a natural-language policy violation.
The document states '语言:中文(默认)/ 英文' and requires an '/en/' prefix for English, which establishes a default locale preference in natural language. Under the policy rule, forcing a specific language without user opt-in can be a locale-policy violation unless clearly justified.
No suspicious patterns detected.