T09 · Insecure Skill Coding Practices
- Location
SKILL.md:16- Finding
Last.fm API Key and Listening Data Transmitted Over Cleartext HTTP
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Last.fm skill is purpose-aligned, but it documents sending the user's API key and listening data over unencrypted HTTP.
Review before installing. Use HTTPS for Last.fm API calls, avoid exposing the expanded URLs in logs, use a dedicated Last.fm API key, and only configure an account whose listening history and profile stats you are comfortable querying through this skill.
SKILL.md:16Last.fm API Key and Listening Data Transmitted Over Cleartext HTTP
The documented base URL and all example curl commands use plain HTTP rather than HTTPS, which exposes requests to interception or modification in transit. Even if the API key is not highly privileged, plaintext transport can leak the user's Last.fm username, API key, listening queries, and returned personal data, and enables man-in-the-middle tampering of responses.
The skill documentation encourages querying user-specific Last.fm endpoints using a username and API key, but it does not clearly warn that listening history, profile statistics, and related metadata are sent to an external third-party service. In this context, the omission can mislead users about the privacy implications of using the skill, especially because the data relates to personal behavioral history and profile information.
No suspicious patterns detected.