T08 · Insecure Dependencies
Warning
- Location
SKILL.md:5- Finding
Unpinned Third-Party Homebrew Dependency
- Content
View full analysis
- Remediation
View remediation
Security audit
spongo
Security checks for vulnerabilities and agentic risk
Overview
The skill is a simple Spotify command-line helper, but it asks users to import Chrome cookies for login without explaining the sensitivity or storage of that session data.
Review this before installing if you are uncomfortable granting a Spotify tool access to Chrome cookies. Prefer the fallback client or an authentication flow that does not read browser cookies, and if using spogo, consider a dedicated browser profile/session and check where the tool stores imported credentials.
Vulnerability Patterns
- Insecure DependenciesIntroduces malicious components through unsafe dependency sources
- Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
- Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
- Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
- Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)
Vulnerability Patterns
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
- 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)
YARA rule 'info_stealer': Information stealer patterns (credential harvesting, browser data theft) [malware]
High
- Category
- YARA Match
- Confidence
- 89% confidence
- Finding
The matched command resembles browser credential extraction behavior because it imports authentication cookies directly from Chrome. In this context the apparent goal is Spotify authentication rather than overt malware, but the mechanism is still dangerous because browser cookies can grant account access and are commonly targeted by infostealers; normalizing this behavior in a skill materially raises the risk of credential theft or unauthorized session reuse.
- Content
md o"],"label":"Install spogo (brew)"},{"id":"brew","kind":"brew","formula":"spotify_player","bins":["spotify_player"],"label":"Install spotify_player (brew)"}]}} --- # spogo / spotify_player Use `spogo` **(preferred)** for Spotify playback/search. Fall back to `spotify_player` if needed. Requirements - Spotify Premium account. - Either `spogo` or `spotify_player` installed. spogo setup - Import cookies: `spogo auth import --browser chrome` Common CLI commands - Search: `spogo search track "query"` - Playback: `spogo play|pause|next|prev` - Devices: `spogo device list`, `spogo device set "<name|id>"` - Status: `spogo status` spotify_player commands (fallback) - Search: `spotify_player search "query"` - Playback: `spotify_player playback play|pause|next|previous` - Connect device: `spotify_player connect` - Like track: `spotify_player like` Notes - Config folder: `~/.config/spotify-player` (e.g., `app.toml`). - For Spotify Connect integration, set a user `client_id` in config. - TUI
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 95% confidence
- Finding
The skill explicitly instructs the user to import browser cookies from Chrome for Spotify authentication, which involves accessing highly sensitive session material. Even if intended for legitimate login reuse, encouraging cookie extraction without warnings, scope limitations, or safer alternatives increases the risk of credential exposure, session hijacking, and misuse by the tool or any compromised environment.
- Content
Static analysis
No suspicious patterns detected.