ClawHub
Back to skill

Security audit

Dokploy

Security checks across malware telemetry and agentic risk

Overview

This Dokploy skill matches its deployment-management purpose, but it needs review because it can store and reveal powerful credentials and raw application secrets.

Install only if you are comfortable giving this skill a Dokploy API key with deployment-management authority. Use the narrowest key available, avoid sharing terminal output from config show, env list, or logs, review every deploy/update/delete command before running it, and consider fixing the plaintext config storage and jq env-delete bug before using it on production systems.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Lp3

Medium
Category
MCP Least Privilege
Confidence
91% confidence
Finding
The skill exposes shell-based operational capabilities and API-driven infrastructure management but does not declare permissions or trust boundaries. This can mislead users and agent platforms about the skill's effective power, increasing the chance of unsafe execution against deployment infrastructure.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The documentation includes destructive operations such as project/application/domain deletion without any warning, confirmation guidance, or rollback considerations. In an agent context, this increases the risk of accidental irreversible actions against live infrastructure if a user or automation invokes the documented commands too casually.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The skill instructs users to export and store a live API key in environment variables and pass it on the command line without warning about shell history, process listing exposure, or secret leakage in logs. Because the token grants management access to Dokploy, exposure could allow unauthorized project, application, domain, or deployment changes.

Missing User Warnings

Medium
Confidence
87% confidence
Finding
The `env list` command fetches and prints all environment variables directly to stdout without any masking or warning, which can expose secrets such as API keys, tokens, and database passwords to terminals, shell history capture, logs, or calling tools. In a deployment-management context, environment variables commonly hold production credentials, so this behavior materially increases secret exposure risk.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The script persists the Dokploy API key in a shell sourceable file under the user's home directory, creating a long-lived plaintext secret on disk. If the file is readable by other local users, included in backups, or accidentally exposed through logs or support bundles, the API key could be stolen and used to manage deployments and infrastructure via the Dokploy API.

Credential Access

High
Category
Privilege Escalation
Content
fi

                local response=$(api_request "GET" "/application.byId?applicationId=$appId")
                local currentEnv=$(echo "$response" | jq -r '.env // {}')
                local newEnv=$(echo "$currentEnv" | jq "del(.$key)")

                local data=$(jq -n --argjson env "$newEnv" '{env: $env}')
Confidence
84% confidence
Finding
.env

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.