Security audit

MP3 Tag Cleaner

Security checks for vulnerabilities and agentic risk

Overview

This MP3 tag cleaner does what it says, but it permanently modifies files in bulk and has weak safeguards around file scope, backups, and temporary-folder deletion.

Review before installing. Use only on backed-up MP3s, inspect the generated file list before running, ensure C:\Temp\MP3Work_ID3 contains nothing important, and compile or verify the executable from the reviewed source rather than trusting an unreviewed binary.

SkillSpector

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
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

Findings (3)

Missing User Warnings

Medium

Confidence: 92% confidence
Finding: The skill performs destructive file modifications by stripping ID3v1/ID3v2 tags, including comments and embedded artwork, but the warning language is not explicit enough about irreversibility and in-place impact on users' media files. This creates a real safety issue because users may trigger bulk processing without understanding that metadata and cover art can be permanently lost if no backup is kept.

Missing User Warnings

Medium

Confidence: 90% confidence
Finding: The program removes ID3 metadata and then overwrites the original file in place with no prompt, backup retention, or explicit confirmation. This is dangerous because metadata deletion is irreversible in normal use and can cause silent data loss or corruption if the parsing/rewrite logic mishandles a file.

Missing User Warnings

Low

Confidence: 83% confidence
Finding: The code recursively deletes a fixed temporary working directory at startup and again in cleanup without warning the user. While the path is hardcoded and not attacker-controlled here, recursive deletion can still destroy unrelated files if the directory is reused, misconfigured, or contains unexpected content.

Static analysis

No suspicious patterns detected.