Security audit

dxyz-cPanel

Security checks across malware telemetry and agentic risk

Overview

This is a real cPanel/WHM administration skill, but it gives broad live server-control power with weak safeguards around destructive actions and credentials.

Install only if you intentionally want an agent to administer a real cPanel/WHM environment. Use a least-privilege, IP-restricted token; verify CPANEL_HOST is the intended HTTPS cPanel/WHM server; avoid storing long-lived tokens in plain config files; do not reuse the example passwords; and require manual confirmation before account deletion, restores, DNS changes, email deletion, database deletion, or password changes.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access

Findings (17)

Lp3

Medium

Category: MCP Least Privilege
Confidence: 95% confidence
Finding: The skill invokes shell execution extensively via the `exec` tool but does not declare corresponding permissions or constraints. This creates a transparency and governance gap: an agent or reviewer may underestimate the skill's ability to run arbitrary commands and perform high-impact administrative actions against remote infrastructure.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The skill advertises destructive administrative actions such as deleting accounts, DNS records, email resources, and restoring backups without any warning, confirmation guidance, or discussion of irreversible effects. In a server-administration skill, this increases the risk of accidental misuse by an agent or operator and could lead to service outages, data loss, or misconfiguration at scale.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The documentation tells users to export a cPanel API token but provides no warning that the token is a high-value secret with broad administrative power. In this context, omission of secure-handling guidance can lead to credential exposure through shell history, logs, screenshots, shared terminals, or insecure storage, enabling unauthorized control of hosting infrastructure.

Missing User Warnings

Medium

Confidence: 81% confidence
Finding: The quick-start examples show live account and email creation against a real cPanel/WHM endpoint and include credentials directly in command lines and URLs. This encourages unsafe operational behavior: shell history exposure, accidental execution against production, and use of weak example passwords without any cautionary guardrails.

Vague Triggers

Medium

Confidence: 86% confidence
Finding: The description is broad enough to match generic server administration requests, while the skill exposes powerful account, file, DNS, SSL, and backup operations through shell-backed API calls. Overbroad routing can cause the skill to activate in situations where user intent is ambiguous, increasing the chance of unintended privileged changes on hosting infrastructure.

Missing User Warnings

High

Confidence: 96% confidence
Finding: The skill documents account termination through `removeacct` without any warning, confirmation step, or mention of irreversible consequences. In a cPanel/WHM context this can delete a customer's hosting account and associated services, making accidental or premature execution highly damaging.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: Restore operations are presented as routine commands without warning that they may overwrite or alter existing account state and content. In hosting environments, restoring the wrong backup or restoring over a live account can cause data loss, service disruption, or rollback of legitimate changes.

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The document includes example curl commands that use live authentication headers with $TOKEN and operational endpoints, but it provides no warning about protecting secrets, avoiding shell history leakage, or redacting tokens from logs and screenshots. In a cPanel/WHM administration skill, this is meaningful because users are likely to copy-paste these commands during real server operations, increasing the chance of credential exposure through terminals, process listings, debug logs, or shared troubleshooting output.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The reference instructs users to export a long-lived API token into a shell environment without any guidance on secrecy, least privilege, rotation, or avoiding shell history/process exposure. In a skill that uses exec/read_file/write_file for live server administration, mishandling this token could enable full WHM/cPanel account takeover and broad server-side actions.

Missing User Warnings

High

Confidence: 94% confidence
Finding: The restore path triggers a destructive account restore operation immediately, with no confirmation prompt, dry-run mode, or explicit safety guard. In a server administration skill that manages cPanel/WHM backups, this increases the chance of accidental restoration, account overwrite, downtime, or data loss if the wrong backup file or user is supplied.

Missing User Warnings

Medium

Confidence: 97% confidence
Finding: The script places the account password directly into the query string of the curl request. URL query parameters are commonly exposed through process listings, shell history, reverse proxies, web server logs, monitoring systems, and debugging output, so this can leak newly created cPanel account credentials even when HTTPS is used. In this skill context, the danger is increased because it performs privileged WHM administration and provisions real hosting accounts.

Missing User Warnings

High

Confidence: 98% confidence
Finding: The script sends the database password in the URL query string when creating a user. Query parameters are commonly exposed through shell history, process listings, proxies, reverse proxies, access logs, monitoring systems, and error telemetry, so credentials can leak beyond the intended recipient. In a cPanel administration skill, this is especially dangerous because the leaked password can grant direct database access and may be reused elsewhere.

Missing User Warnings

Medium

Confidence: 87% confidence
Finding: The script performs database deletion immediately with no confirmation prompt, dry-run mode, safeguard flag, or explicit warning. In an agent-executed server administration context, this increases the chance of accidental destructive actions from malformed input, user misunderstanding, or automation mistakes, leading to irreversible data loss and service disruption.

Missing User Warnings

Medium

Confidence: 89% confidence
Finding: The script performs DNS record deletion immediately based on a supplied line number, with no confirmation prompt, dry-run mode, or explicit warning. In a server administration skill with live cPanel access, this increases the chance of accidental or scripted destructive changes that can disrupt email delivery, web routing, or service availability.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The script reads a cPanel API token from the environment and sends it to the host specified by CPANEL_HOST without validating or constraining the destination. If CPANEL_HOST is attacker-controlled or misconfigured, the token can be exfiltrated to an arbitrary server, giving unauthorized access to cPanel/WHM functions.

Missing User Warnings

Medium

Confidence: 98% confidence
Finding: Passwords are placed directly into the URL query string for account creation, which is unsafe because URLs may be exposed via shell history, process listings, proxy logs, web server logs, and monitoring systems. In a hosting administration context, this can disclose mailbox credentials and enable account takeover across email and potentially reused passwords elsewhere.

Missing User Warnings

Medium

Confidence: 97% confidence
Finding: The password-change operation also places the new password in the URL query string, creating the same credential exposure risks as the create path. This is particularly sensitive because it changes live account credentials and could leak freshly set passwords to logs or intermediary systems.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.