T03 · Remote Payload Retrieval and Execution
- Location
references/cli-setup.md:16- Finding
Remote Installer Piped Directly into Bash Without Integrity Verification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent Bright Data scraping documentation, but its setup guidance includes unsafe remote and unpinned CLI execution patterns users should review before installing.
Install only if you are comfortable using Bright Data for web scraping and sharing requested URLs or search inputs with that service. Prefer pinned, reviewable CLI installation methods over curl-to-bash or unpinned npx, avoid hardcoding credentials in URLs or source files, and keep Bright Data API keys and browser passwords out of logs, prompts, and repositories.
references/cli-setup.md:16Remote Installer Piped Directly into Bash Without Integrity Verification
references/cli-setup.md:21Unpinned Bright Data CLI Package Is Automatically Downloaded and Executed
Referenced artifact was not completely inspected
See **[references/browser-api.md](references/browser-api.md)** for complete reference including all CDP functions, bandwidth optimization, CAPTCHA patterns, and
Referenced artifact was not completely inspected
See **[references/browser-api.md](references/browser-api.md)** for complete reference including all CDP functions, bandwidth optimization, CAPTCHA patterns, and
curl ... | bash executes a remote script directly with no integrity verification, pinning, or review step. If the hosting domain, network path, or served script is compromised, users could run arbitrary attacker-controlled code during setup.
npm install -g @brightdata/cli
**Curl installer (macOS/Linux):**
```bash
curl -fsSL https://cli.brightdata.com/install.sh | bash
The | bash chain is the dangerous execution step that turns remote content retrieval into immediate code execution. In a skill intended for coding assistants and developers, this is more dangerous because it may be copied verbatim into automated or semi-automated workflows without scrutiny.
Curl installer (macOS/Linux):
curl -fsSL https://cli.brightdata.com/install.sh | bash
One-off (no install):
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
The zones probe is the most reliable auth check: it requires valid credentials and returns quickly.
**Config file locations:**
- Linux: `~/.config/brightdata-cli/credentials.json`
- macOS: `~/Library/Application Support/brightdata-cli/credentials.json`
- Windows: `%APPDATA%\brightdata-cli\credentials.json`
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
The zones probe is the most reliable auth check: it requires valid credentials and returns quickly.
**Config file locations:**
- Linux: `~/.config/brightdata-cli/credentials.json`
- macOS: `~/Library/Application Support/brightdata-cli/credentials.json`
- Windows: `%APPDATA%\brightdata-cli\credentials.json`
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
The zones probe is the most reliable auth check: it requires valid credentials and returns quickly.
**Config file locations:**
- Linux: `~/.config/brightdata-cli/credentials.json`
- macOS: `~/Library/Application Support/brightdata-cli/credentials.json`
- Windows: `%APPDATA%\brightdata-cli\credentials.json`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Submit
response = requests.post(
"https://api.brightdata.com/request",
params={"async": "1"},
headers={"Authorization": f"Bearer {API_KEY}"},
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Sync (up to 20 URLs, returns immediately)
response = requests.post(
"https://api.brightdata.com/datasets/v3/scrape",
params={"dataset_id": "YOUR_DATASET_ID", "format": "json"},
headers={"Authorization": f"Bearer {API_KEY}"},
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import time
# Trigger
snapshot_id = requests.post(
"https://api.brightdata.com/datasets/v3/trigger",
params={"dataset_id": DATASET_ID, "format": "json"},
headers={"Authorization": f"Bearer {API_KEY}"},
This markdown file includes connection strings that embed ${AUTH} directly in WebSocket/HTTPS URLs, and later examples hardcode username:password values into those endpoints. While the file explains how to authenticate, it does not clearly warn readers that embedding credentials in URLs or source examples can expose secrets via logs, shell history, screenshots, or copied code.
The documentation demonstrates sending a base64-encoded client certificate and private key to Browser.addCertificate without any warning about secure key handling. In an assistant-driven coding workflow, users may copy this literally and embed private keys in code, repositories, prompts, logs, or telemetry, creating a realistic secret-exposure risk.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
Browser.addCertificateInstall a client SSL/TLS certificate for authenticated domain access. Certificate is automatically removed when the session ends.
await client.send("Browser.addCertificate", {
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## REST API (Recommended)
**Endpoint:** `POST https://api.brightdata.com/request`
**Header:** `Authorization: Bearer YOUR_API_KEY`