Youtube Analytics CLI

Security checks across malware telemetry and agentic risk

Overview

The skill appears to be a disclosed YouTube analytics integration, but users should handle OAuth credentials carefully and invoke it only for analytics tasks.

Install if you specifically want YouTube Analytics help. Use least-privilege OAuth scopes, keep credentials and refresh tokens out of chat/logs, restrict permissions on local credential files, and avoid using this skill for ordinary YouTube questions that do not require account analytics.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Confidence
92% confidence
Finding
The trigger list includes very broad terms such as "YouTube" that can match many ordinary requests and cause the skill to activate outside its intended scope. Over-broad activation increases the chance an agent unnecessarily installs or invokes external tooling and may prompt for credentials in contexts where the user did not explicitly ask for YouTube analytics actions.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The skill instructs the agent to use OAuth client secrets, refresh tokens, environment variables, and a local credentials file, but it provides no safety guidance on secret minimization, redaction, storage permissions, or prohibitions on printing sensitive values. In an agent setting, this can lead to accidental disclosure of long-lived credentials in logs, command output, chat transcripts, or overly broad file access attempts.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal