T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:17- Finding
Unverified Remote Installer Executed Directly by Bash
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent Cursor CLI guide, but it recommends unsafe installation and automation patterns that can execute unverified code or bypass workspace trust review.
Review this skill carefully before installing. Prefer a package-managed or verified Cursor CLI installer instead of `curl | bash`, do not automate workspace trust approval for unreviewed repositories, and avoid `--force` unless you are working in a controlled branch or sandbox with review and rollback available.
SKILL.md:17Unverified Remote Installer Executed Directly by Bash
README.md:29Quick Start Executes a Mutable Remote Installer Without Verification
SKILL.md:172Automation Unconditionally Accepts Workspace Trust
This is a direct example of external script fetching followed by execution: curl https://cursor.com/install -fsS | bash. That pattern creates a strong supply-chain and remote-code-execution risk because the fetched content is not pinned, authenticated beyond TLS, or validated before being run.
Install the Cursor CLI:
# Standard installation (macOS, Linux, WSL)
curl https://cursor.com/install -fsS | bash
# Homebrew (macOS only)
brew install --cask cursor-cli
The | bash construct is dangerous because it turns network-retrieved data into immediately executed shell code with no review boundary. In the context of a developer skill, this is especially risky because users may copy-paste the command into privileged environments, CI runners, or workstations, magnifying the blast radius of any compromise.
Install the Cursor CLI:
# Standard installation (macOS, Linux, WSL)
curl https://cursor.com/install -fsS | bash
# Homebrew (macOS only)
brew install --cask cursor-cli
curl https://cursor.com/install -fsS | bash fetches remote content and immediately executes it without independent verification. If the server, transport, installer, or DNS path is compromised, users may execute attacker-controlled code on their machine.
curl https://cursor.com/install -fsS | bash
The | bash chaining pattern turns a network fetch directly into code execution, eliminating opportunities for review and integrity validation. In a skill intended to guide automation and engineering workflows, this is especially dangerous because users are likely to copy-paste it verbatim.
curl https://cursor.com/install -fsS | bash
Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
Use a specific model:
agent --model gpt-5
Switch models during a session:
Automating the workspace trust prompt by blindly sending a bypasses a security decision intended to protect users from untrusted projects. Trusting a workspace can enable execution of project-defined rules, commands, or integrations, so this guidance normalizes unsafe approval without review.
The README instructs users to download and immediately execute a remote script via a shell pipeline, with no integrity verification, content inspection, or warning about the trust implications. If the remote endpoint, distribution path, or network path is compromised, users could execute arbitrary code on their systems during installation.
Documenting --force as auto-applying changes without confirmation encourages unattended modification of code or project files. In an agent automation context, this increases the chance of unintended edits, destructive changes, or unsafe actions being applied without human review.
agent -p 'Run tests' --output-format stream-json --stream-partial-output
**Force mode (auto-apply changes without confirmation):**
```bash
agent -p 'Fix all linting errors' --force
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# 1. Install tmux if not available
sudo apt install tmux # Ubuntu/Debian
brew install tmux # macOS
# 2. Create a tmux session
The documented tmux kill-session -t cursor command is destructive and can terminate an existing session without checking whether it contains in-progress work. In an automation-focused skill, readers may copy this verbatim, causing accidental loss of state, commands, or unsaved terminal work.
No suspicious patterns detected.