Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent x-cmd helper, but it includes an agent-usable remote installer path that can execute mutable downloaded shell code before independent verification.
Review before installing. Prefer `brew install x-cmd` or a manual download-and-review flow, avoid the `curl | sh` auto-install path on machines with secrets, and do not let an agent install x-cmd or packages unless you explicitly requested that action and trust the package sources.
data/install.md:104Unverified Remote Installer Piped Directly into a Shell
The skill includes a direct 'curl | sh' installation command that fetches and immediately executes remote code. Even though the document warns about the risk, embedding this pattern in an agent skill is dangerous because compromised infrastructure, DNS/TLS interception, or supply-chain abuse could lead to arbitrary code execution in the user's environment.
recommendation: "acceptable with review"
requires_review: true
- name: install-script-auto
command: "curl -fsSL https://get.x-cmd.com | sh"
verification: checksum
risk_level: high
recommendation: "avoid in sensitive environments"
This fetches an external install script to a temporary file for later review and execution. It is safer than piping directly to a shell, but it still introduces supply-chain risk and may normalize execution of untrusted downloaded code, especially if an agent later automates the review step inadequately.
# 1. Download install script
curl -fsSL https://get.x-cmd.com > /tmp/x-cmd-install.sh
# 2. REVIEW the script content (critical step)
cat /tmp/x-cmd-install.sh
The '| sh' construct is a classic dangerous chaining pattern because it turns network-delivered content directly into shell execution without an inspection boundary. In an agent skill, this is especially risky because users may authorize the skill broadly and the command can execute arbitrary attacker-controlled code if the remote endpoint is compromised.
⚠️ WARNING: This executes remote code without manual review.
curl -fsSL https://get.x-cmd.com | sh
Only use when:
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
x-cmd is entirely contained in ~/.x-cmd.root/. To remove:
rm -rf ~/.x-cmd.root/
# Also remove from shell config (~/.bashrc, ~/.zshrc):
# [ ! -f "$HOME/.x-cmd.root/X" ] || . "$HOME/.x-cmd.root/X"
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
x-cmd is entirely contained in ~/.x-cmd.root/. To remove:
rm -rf ~/.x-cmd.root/
# Also remove from shell config (~/.bashrc, ~/.zshrc):
# [ ! -f "$HOME/.x-cmd.root/X" ] || . "$HOME/.x-cmd.root/X"
The skill explicitly tells users to source ~/.x-cmd.root/X, which executes local shell code and alters the current shell environment, including PATH. Sourcing a script is more dangerous than invoking a standalone command because any code in that file runs with the user's privileges in the current shell session, and the documentation does not clearly warn about the trust boundary or the environment modifications being made.
The skill advertises x env use <pkg> and x pixi use <pkg> as instant installation mechanisms without clearly warning that these commands fetch and install external software onto the user's machine. This creates supply-chain and execution risk, especially for AI agents or users who may treat package names as harmless suggestions and install unreviewed software into a PATH-accessible location.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
1. Creates `~/.x-cmd.root/` directory (user-local)
2. Downloads x-cmd core files from GitHub releases
3. Verifies SHA256 checksums of all downloaded files
4. No system modifications, no sudo required
---
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
1. Creates `~/.x-cmd.root/` directory (user-local)
2. Downloads x-cmd core files from GitHub releases
3. Verifies SHA256 checksums of all downloaded files
4. No system modifications, no sudo required
---
No suspicious patterns detected.