T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:14- Finding
Mandatory Overbroad Cloudflare Configuration Reconnaissance
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Cloudflare management skill is mostly coherent, but it asks agents to use powerful Cloudflare credentials with broad zone-wide preflight reads and includes an unsafe optional npx fallback.
Install only if you are comfortable giving the agent Cloudflare API access for the target zone. Use narrowly scoped Cloudflare tokens, avoid the `npx json` fallback, review every planned DNS/security change before execution, and ask the agent to query only the records or settings needed for your specific task.
SKILL.md:14Mandatory Overbroad Cloudflare Configuration Reconnaissance
SKILL.md:32Unpinned Third-Party Package Retrieval and Execution Through npx
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
This skill uses `curl` and `jq` for Cloudflare API interactions. On Windows (without WSL), `jq` may not be available.
**Alternatives when `jq` is not installed:**
- Use `python3 -m json.tool` for basic JSON formatting: `curl ... | python3 -m json.tool`
- Use `npx json` (from the `json` npm package): `curl ... | npx json`
- Use PowerShell's `ConvertFrom-Json`: `(curl ... | ConvertFrom-Json)`
The skill recommends npx json without pinning a specific package version. Because npx may fetch and execute the latest package from the registry at runtime, a compromised or changed upstream package could lead to arbitrary code execution on the operator's machine.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use:
https://api.cloudflare.com/client/v4
Auth header:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X POST \
"https://api.cloudflare.com/client/v4/zones/$CLOUDFLARE_ZONE_ID/dns_records" \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X POST \
"https://api.cloudflare.com/client/v4/zones/$CLOUDFLARE_ZONE_ID/dns_records" \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-H "Content-Type: application/json" \
The skill includes a destructive DNS deletion command but the command block itself does not require an immediate, explicit confirmation warning or strong guardrails. In an agentic context, deleting the wrong DNS record can cause outage, misrouting, or loss of email/web service availability.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
This is required when proxying through Cloudflare to Vercel:
curl -s -X PATCH \
"https://api.cloudflare.com/client/v4/zones/$CLOUDFLARE_ZONE_ID/settings/ssl" \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X PATCH \
"https://api.cloudflare.com/client/v4/zones/$CLOUDFLARE_ZONE_ID/settings/always_use_https" \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X PATCH \
"https://api.cloudflare.com/client/v4/zones/$CLOUDFLARE_ZONE_ID/settings/browser_cache_ttl" \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Use after major deployments:
curl -s -X POST \
"https://api.cloudflare.com/client/v4/zones/$CLOUDFLARE_ZONE_ID/purge_cache" \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Use after major deployments:
curl -s -X POST \
"https://api.cloudflare.com/client/v4/zones/$CLOUDFLARE_ZONE_ID/purge_cache" \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Protect API routes from abuse:
curl -s -X POST \
"https://api.cloudflare.com/client/v4/zones/$CLOUDFLARE_ZONE_ID/rulesets/phases/http_ratelimit/entrypoint" \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-H "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X PUT \
"https://api.cloudflare.com/client/v4/zones/$CLOUDFLARE_ZONE_ID/bot_management" \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-H "Content-Type: application/json" \
No suspicious patterns detected.