Security audit

Cf Workers Logs

Security checks across malware telemetry and agentic risk

Overview

This skill does what it says: it helps query Cloudflare Workers logs, but the logs and API token should be treated as sensitive.

Install only where the agent is allowed to access Cloudflare Workers logs. Use a dedicated, narrowly scoped Cloudflare API token, keep .env files out of version control, avoid putting secrets in application logs, and prefer specific worker names, short time windows, and low result limits when querying.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (2)

Missing User Warnings

Medium

Confidence: 87% confidence
Finding: The README encourages querying observability logs and displaying results in the terminal, but it does not warn that logs frequently contain sensitive data such as tokens, user identifiers, request payloads, stack traces, or internal system details. In an agent skill context, this increases the chance that sensitive information is retrieved and surfaced to the model or terminal output without redaction, especially during broad searches or error investigations.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The skill explicitly instructs the agent to grep project .env files for Cloudflare credentials if environment variables are not already present. Accessing local secret files without an explicit user warning or consent can expose unrelated secrets in the workspace and expands the blast radius beyond the minimum credentials needed for the task.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal