Back to skill

Security audit

last.fm

Security checks for vulnerabilities and agentic risk

Overview

This is a simple Last.fm API reference skill with no code execution, persistence, or hidden behavior, though users should be mindful that some documented endpoints expose profile and listening-history data.

Installers should treat this as a Last.fm API reference. Use a Last.fm API key intentionally, avoid sharing or storing it unnecessarily, and only request user profile or listening-history data when the affected user expects that data to be queried or displayed.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill documents several Last.fm endpoints that retrieve user profile details and listening-history data, but it provides no privacy warning, consent guidance, or data-handling limitations. In an agent/skill context, this omission can encourage collection or display of personal behavioral data without informing users, increasing privacy and compliance risk even though the API usage itself is not inherently malicious.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.