T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:16- Finding
Remote Installer Executed Without Integrity Verification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a real Cursor CLI guide, but it includes unsafe installation and automation steps that deserve review before use.
Install only after reviewing the installer path and automation workflow. Prefer a package-managed or verified Cursor CLI install, do not pipe remote scripts directly into a shell, do not auto-trust unknown workspaces, and avoid `--force` except in isolated repositories with version control and reviewed scope.
SKILL.md:16Remote Installer Executed Without Integrity Verification
README.md:28Quick Start Executes a Mutable Remote Installer Directly in Bash
SKILL.md:198Automation Unconditionally Accepts Workspace Trust
The command fetches an external script from the internet and executes it in a shell in a single step. This creates a direct remote code execution path for anyone following the documentation, making compromise of the distribution endpoint or content highly impactful.
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 pipe into bash is the risky chaining behavior because it removes any opportunity for the user or tooling to review the downloaded content before execution. In a developer-focused skill, this is especially dangerous because users may copy-paste commands with elevated trust and potentially broad local access.
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 executes it immediately without verification, which is a well-known supply-chain risk. If the server, transport, or distribution path is compromised, arbitrary code runs on the user's machine instantly.
curl https://cursor.com/install -fsS | bash
The | bash chaining pattern directly executes downloaded data as shell code, eliminating opportunities for inspection or integrity checks. In a skill that may be used by automation-oriented users, this pattern is particularly dangerous because it normalizes unsafe command execution habits.
curl https://cursor.com/install -fsS | bash
The tmux automation instructs users to send a to trust the workspace automatically, bypassing an important security gate. Workspace trust controls are intended to prevent execution or elevated access in untrusted repositories, so auto-acceptance can expose users to malicious project configuration, scripts, or tool behavior.
The README instructs users to pipe a remote script directly into bash, which executes network-fetched code without inspection, signature verification, or integrity checks. If the remote host, transport, or served script is compromised, users could run arbitrary code on their machines immediately.
Describing auto-apply behavior 'without confirmation' encourages autonomous modification of code and files without a review checkpoint. In an agent skill focused on software engineering automation, this is especially risky because prompts can trigger broad changes that may introduce vulnerabilities or damage the workspace.
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
The documentation recommends --force to auto-apply changes without confirmation but does not warn that this can modify files without human review. In automation or CI contexts, this increases the chance of unsafe, destructive, or security-relevant changes being applied silently.
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
No suspicious patterns detected.