Pi-hole Control
Security checks across malware telemetry and agentic risk
Overview
The skill is purpose-aligned for controlling Pi-hole, but a command bug can disable blocking indefinitely when a timed disable is requested, and its API password handling is less safe than claimed.
Only install this if you are comfortable granting the agent control over your Pi-hole. Treat `off`/`disable` commands carefully until the timed-disable bug is fixed, avoid `insecure: true` unless you trust the local network, and consider rotating the Pi-hole app password after testing.
VirusTotal
65/65 vendors flagged this skill as clean.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A user or agent asking to disable Pi-hole for a limited time, such as 30 minutes, may instead turn off DNS blocking indefinitely across the network.
In a bash case statement, the first matching pattern wins, so `disable` is handled as an indefinite disable and the later custom-duration branch is unreachable.
off|disable)
# Disable Pi-hole blocking (indefinitely)
...
disable)
# Disable for custom duration (in minutes)Fix the command routing so `disable <minutes>` reaches the timed branch, reserve `off` for indefinite disable, and consider requiring explicit confirmation for indefinite disabling.
The Pi-hole API credential could be exposed locally and may allow control of blocking state or access to query/statistics data.
The Pi-hole app password is expanded directly into curl's command-line arguments, which can be visible to other local processes or users while the command runs.
curl $CURL_FLAGS ... -d "{\"password\":\"$PIHOLE_API_TOKEN\"}" ... "${PIHOLE_API_URL}/auth"Pass the password via stdin or another mechanism that does not place it in argv, properly JSON-escape it, and declare the credential requirement in metadata.
Users may underestimate the local credential-exposure risk because the documentation overstates the protection provided.
This safety claim is contradicted by the script's curl invocation, which expands the token into a `-d` command-line argument.
Token is not visible in process list (passed via environment)
Update the documentation to accurately describe credential handling, and only claim process-list protection after changing the implementation.
Installation may fail or require manual setup that is not visible from the registry metadata alone.
The skill itself discloses required tools and credentials, but the registry metadata lists no required binaries, env vars, or primary credential.
Requirements - Pi-hole v6 or later - App password generated in Pi-hole Admin - Network access to Pi-hole API - `curl`, `jq`
Declare curl, jq, and the Pi-hole API credential/config requirements in the skill metadata.