ClawHub
Back to skill

Security audit

Spotify

Security checks across malware telemetry and agentic risk

Overview

This Spotify helper is mostly understandable, but it asks users to install an unprovided command with sudo and store Spotify credentials without permission guidance.

Review the actual spotify script before installing it, avoid system-wide install steps where possible, prefer a virtual environment or pipx instead of --break-system-packages, and restrict the config file permissions such as chmod 600 ~/.config/spotify-cli/config.

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 (1)

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill instructs users to place Spotify client credentials in a plaintext config file under their home directory without mentioning file permissions, secret storage, or alternatives such as environment variables or a keyring. While Spotify API client secrets are not typically system-compromise secrets, disclosure can enable unauthorized use of the developer app, token abuse, and account or quota misuse, especially on shared systems or in environments where home directories are backed up or exposed.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.