Back to skill

Security audit

Dev.to

Security checks for vulnerabilities and agentic risk

Overview

This Dev.to connector skill is coherent, but its setup instructions include direct execution of remote installer scripts, so users should review it before installing.

Review the setup path before installing. Prefer an official versioned or verifiable oo CLI installation method, avoid letting an agent run the remote installer automatically, and confirm exact payloads before allowing article creation or updates.

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Findings (1)

T03 · Remote Payload Retrieval and Execution

Error
Location
SKILL.md:63
Finding

Unverified Remote Installer Scripts Executed Directly by Shells

Content
View full analysis
): ```bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux ``` ```powershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell ``` ``` ### Technical Analysis The installation instructions download mutable scripts from an external server and immediately execute them through Bash or PowerShell. No fixed release version, cryptographic checksum, digital signature, or manual inspection step is required before execution. Although `cli.oomol.com` is consistent with the declared OOMOL service, these instructions make the code ultimately executed depend on whatever the remote server returns at installation time. The executed payload can therefore change after the Skill has been reviewed. Compromise of the hosting infrastructure, deployment pipeline, DNS resolution, or applicable TLS trust chain could convert the documented installation process into arbitrary code execution. Installing a required CLI may be necessary for the Skill's functionality. However, direct network-to-shell execution exceeds the minimum privilege and trust necessary because safer package retrieval, integrity verification, and explicit user approval mechanisms are available. ### Attack Path 1. The `oo` command is unavailable, causing the user or agent to consult the first-time setup instructions. 2. An attacker compromises or gains influence over the remote installer response, its deployment pipeline, domain resolution, or another relevant delivery component. 3. The user runs the documented `curl | bash` or `irm | iex` command. 4. The shell executes the response without verifying a pinned artifact, checksum, or signature. 5. The payloa ...[truncated 894 chars]
Remediation
View remediation
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The skill instructs running a remote installation script via curl ... | bash, which executes code fetched over the network without prior verification. If the hosting endpoint, transport, or supply chain is compromised, this can lead to arbitrary code execution on the user's machine; the risk is heightened because the skill is operational and encourages shell execution as part of setup.

Content

Scanner excerpt · SKILL.md (reported line 66)May include surrounding context.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The description says to use this skill for "ANY Dev.to request" and "Whenever a task involves Dev.to," which is very broad and lacks constraints or exclusion conditions. In a manifest/markdown context, this can overlap with many ordinary requests involving Dev.to and does not clarify activation boundaries.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.