Exposed secret literal
Critical
- Finding
- File appears to expose a hardcoded API secret or token.
cloudflare-workers
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This is a coherent documentation-only Cloudflare Workers skill, but it can guide real Cloudflare deployments and credential-backed account changes, so production actions should be reviewed.
Install only if you want the agent to help with Cloudflare Workers development and deployment. Use scoped Cloudflare tokens, review any production deploy, rollback, secret deletion, or CI/CD change before it runs, and avoid copying logging examples without first removing sensitive data from logs.
Static analysis
VirusTotal
VirusTotal findings are pending for this skill version.
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.
What this means
If the agent uses a broadly scoped token, mistakes could change or deploy resources in the user's Cloudflare account.
Why it was flagged
The skill clearly declares Cloudflare credentials that enable deployment or upload operations against a Cloudflare account.
Skill content
primaryEnv: CLOUDFLARE_API_TOKEN ... description: Cloudflare API token (scoped). Required for wrangler deploy/upload.
Recommendation
Use least-privilege Cloudflare API tokens limited to the intended account, Worker, and environment, and require review before production deploys.
What this means
Running the wrong command could deploy unintended code, modify production traffic, or remove secrets from a Worker project.
Why it was flagged
The documentation includes CLI examples that can mutate production deployments or delete configured secrets. These are expected for a deployment skill, but they are high-impact operations.
Skill content
wrangler deploy --env production ... wrangler secret delete API_KEY
Recommendation
Treat deploy, rollback, version rollout, and secret-deletion commands as approval-required actions; prefer dry runs, staging environments, and backups where possible.
What this means
Users depend on the integrity of the installed Wrangler package and its dependencies.
Why it was flagged
The skill instructs installation of npm packages for Wrangler usage. This is central to the purpose, but it relies on the npm package supply chain and unpinned install examples.
Skill content
npm install -g wrangler ... npm install --save-dev wrangler
Recommendation
Install Wrangler from the official package, consider project-local pinned versions for CI, and review lockfiles in production projects.
What this means
Logs may include URLs, methods, error messages, stack traces, or other metadata that could contain sensitive information if copied directly into a project.
Why it was flagged
The observability examples show sending request and error metadata to external log services using declared log tokens.
Skill content
await fetch("https://logs.example.com/ingest", { ... "Authorization": `Bearer ${this.env.LOG_TOKEN}`, ... body: JSON.stringify(entry) })Recommendation
Scrub secrets and personal data from logs, restrict log-token permissions, and send logs only to trusted destinations with appropriate retention controls.