T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:18- Finding
Unverified Remote Installer Is Piped Directly into Bash
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent SEO audit helper, but it needs Review because it includes an unsafe remote installer command and shell-command patterns that can mishandle untrusted URLs or keywords.
Review this before installing. Use a trusted, verifiable method to install Bright Data CLI instead of running the embedded pipe-to-Bash command, and only audit domains or keywords you are comfortable sending through Bright Data and search services. Avoid private/internal URLs unless you have confirmed the tool and account policy allow that use.
SKILL.md:18Unverified Remote Installer Is Piped Directly into Bash
references/bdata-recipes.md:105User-Controlled Audit Inputs Are Unsafely Interpolated into Shell Commands
The skill includes a 'curl | bash' installation command that downloads and immediately executes a remote script. If the remote host, TLS chain, CDN path, or install script is compromised, users can execute arbitrary code on their machine with the privileges of the invoking shell.
The user must have the Bright Data CLI installed and authenticated:
curl -fsSL https://cli.brightdata.com/install.sh | bash
bdata login
The explicit shell chaining pattern '| bash' removes the user's opportunity to inspect downloaded content before execution and is a classic unsafe command-execution anti-pattern. In this skill's context, the danger is amplified because the text presents the command as a prerequisite, making users more likely to run it without scrutiny.
The user must have the Bright Data CLI installed and authenticated:
curl -fsSL https://cli.brightdata.com/install.sh | bash
bdata login
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
"Runs bdata scrape https://example.com/sitemap.xml first for URL discovery, not homepage-only",
"Applies stratified sampling across path-prefix groups (default 10-15 pages)",
"Issues all bdata scrape calls for the sample in parallel (single Bash message, multiple tool calls)",
"Uses bdata scrape -f html to detect JS-injected schema markup (no caveat needed)",
"Follows audit priority order: crawlability first, then technical, on-page, content, authority",
"Checks robots.txt and XML sitemap with bdata scrape",
"Evaluates title tags, meta descriptions, heading structure",
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
"Runs bdata scrape https://example.com/sitemap.xml first for URL discovery, not homepage-only",
"Applies stratified sampling across path-prefix groups (default 10-15 pages)",
"Issues all bdata scrape calls for the sample in parallel (single Bash message, multiple tool calls)",
"Uses bdata scrape -f html to detect JS-injected schema markup (no caveat needed)",
"Follows audit priority order: crawlability first, then technical, on-page, content, authority",
"Checks robots.txt and XML sitemap with bdata scrape",
"Evaluates title tags, meta descriptions, heading structure",
The trigger list is extremely broad and includes vague phrases like 'help with SEO' or 'my SEO is bad', which can cause the skill to activate in contexts where the user did not intend a live web audit. Because this skill performs external Bright Data scraping and SERP queries, over-triggering increases the chance of unnecessary third-party data access, cost, and privacy exposure.
The skill metadata and description do not clearly warn that using the skill causes live third-party requests to Bright Data and may query search engines. Users may disclose domains, URLs, or business-sensitive SEO targets without understanding that external services will be contacted, undermining informed consent and increasing privacy/compliance risk.
The recipe explicitly directs the agent to invoke curl for HTTP status checks, expanding execution beyond the declared Bright Data CLI-only audit scope. Allowing arbitrary subprocess/network tooling increases attack surface and can bypass the skill's intended controls, making it easier for a prompt-influenced workflow to perform unsanctioned requests or use a less governed tool path.
No suspicious patterns detected.