T09 · Insecure Skill Coding Practices
- Location
scripts/batch_rename.py:46- Finding
Path Traversal and File Overwrite Through Unvalidated Rename Parameters
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a local batch file tool, but it can overwrite, move, or corrupt many user files without enough safeguards.
Review before installing. Use this only on copied folders or backed-up data, run --dry-run first, avoid using it on important originals, and do not rely on it to preserve GIF/BMP formats or existing PDFs. Prefer waiting for a version that defaults to safe output folders, pins dependencies, validates rename paths, checks collisions, and implements real backups or rollback.
scripts/batch_rename.py:46Path Traversal and File Overwrite Through Unvalidated Rename Parameters
scripts/convert_to_pdf.py:75Predictable Shared Temporary File Enables File Clobbering and Race Conditions
scripts/image_compress.py:41In-Place Image Processing Can Irreversibly Corrupt BMP and GIF Files
README.md:30Unpinned Third-Party Dependencies Create Supply-Chain and Reproducibility Risk
scripts/convert_to_pdf.py:47PDF Conversion Silently Replaces Existing Output Files
The finding specifically notes safety-signaling language such as 'safe' and mentions backup behavior that may not actually occur while originals are overwritten. False assurances around backup and safety are particularly dangerous for batch file processors because they can directly cause irreversible user data loss.
The finding specifically notes safety-signaling language such as 'safe' and mentions backup behavior that may not actually occur while originals are overwritten. False assurances around backup and safety are particularly dangerous for batch file processors because they can directly cause irreversible user data loss.
The finding specifically notes safety-signaling language such as 'safe' and mentions backup behavior that may not actually occur while originals are overwritten. False assurances around backup and safety are particularly dangerous for batch file processors because they can directly cause irreversible user data loss.
The finding specifically notes safety-signaling language such as 'safe' and mentions backup behavior that may not actually occur while originals are overwritten. False assurances around backup and safety are particularly dangerous for batch file processors because they can directly cause irreversible user data loss.
The checklist exposes what appears to be a personal account identifier in plain text: 'ClawHub account login (lx19840614)'. Even if it is only a username and not a password, publishing account identifiers helps attackers enumerate valid accounts, target credential-stuffing or phishing attacks, and associate a real individual with the asset. In a commercial skill-release context, this makes the account and related dashboard actions more attractive targets.
The skill advertises file-manipulation behavior but does not declare an explicit tool scope such as permissions or allowed-tools. In a batch-processing context, undeclared read/write capability increases the chance of unintended or overly broad filesystem access, making user consent and policy enforcement weaker.
An overly broad description can cause the skill to be invoked for generic file-related requests beyond its safe or intended scope. In a filesystem-modifying tool, over-triggering increases the chance that users run batch operations in inappropriate contexts or on unintended directories.
The skill performs or advertises batch rename, compression, conversion, and organization workflows, all of which can modify or overwrite large numbers of files, yet the description lacks a strong upfront destructive-operation warning. In batch contexts, insufficient warning materially raises the risk of accidental data loss at scale.
The tool advertises support for GIF and BMP and comments imply original formats are preserved, but the implementation writes all non-JPEG inputs using PNG encoding back to the original path. This can corrupt files or produce mislabeled content (for example, a .gif or .bmp file containing PNG data), causing data loss, application failures, and unexpected behavior during batch processing.
The script overwrites original images in place during batch processing without a real backup or a clear destructive-operation warning. In this skill context, marketed as a one-click newbie-friendly file tool, that makes accidental irreversible data loss more likely because users may process entire folders expecting safe compression rather than permanent modification.
This markdown file uses English throughout for operational instructions, checklists, and user-facing planning content, but it does not indicate that English is optional or required for a justified region-specific reason. Under the language/locale policy check, forcing a single language without opt-in can be a natural-language policy violation.
The line states that for TXT/MD conversion, 'English works best,' which expresses a language preference in the skill description. Under the policy, forcing or preferring a specific language without explicit user choice can be a natural-language policy issue, especially since no opt-in or alternative language support choice is offered here.
No suspicious patterns detected.