T09 · Insecure Skill Coding Practices
- Location
SKILL.md:113- Finding
Archive Passwords Exposed Through Command-Line Arguments
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This RAR helper is mostly purpose-aligned, but it teaches risky password handling and persistent environment changes without enough guardrails.
Install only if you are comfortable supervising commands before execution. Avoid putting real archive passwords directly in command arguments, prefer interactive prompts or approved secret handling, do not allow persistent PATH changes unless you intend them and know how to undo them, and verify any downloaded WinRAR/RAR installer through trusted channels before running it.
SKILL.md:113Archive Passwords Exposed Through Command-Line Arguments
Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
- `a`: add files to archive
- `-p`: provide password
- `-ibck`: background mode on Windows
- `-o+`: overwrite existing files
- `-y`: answer yes to prompts
## Encoding tip for Chinese paths on Windows
The skill description is broad enough to activate on general archive-related tasks, not just narrow RAR/WinRAR operations. That can cause the agent to apply risky behaviors from this skill—such as PATH modification, installer download guidance, and password-bearing command construction—in situations where a safer or more appropriate archive workflow should have been used.
The skill recommends persistent PATH modification via setx PATH without warning about system-wide side effects or validating the added directory. Persistent PATH changes can break other tooling, create long-lived environment drift, and increase risk if an unintended or attacker-controlled directory is inserted ahead of trusted executables.
The skill normalizes downloading platform binaries/installers directly from URLs as an operational fallback, with no integrity verification, trust warning, or requirement for user consent. This encourages supply-chain risk and unsafe execution behavior, especially in automated contexts where an agent may move from missing dependency detection to software acquisition and potential execution.
The template demonstrates passing an archive password directly on the command line (-p"p@ss!word"), which can expose the secret through shell history, process listings, logs, screenshots, or copied terminal transcripts. In this skill's context, the risk is elevated because it is an execution template intended for automation and copy-paste use, making insecure secret-handling practices more likely to be propagated into real workflows.
The reference includes commands that place archive passwords directly on the command line (for example -pPASSWORD and concrete password examples) without warning that CLI arguments may be exposed through shell history, logs, job runners, telemetry, and process listings. In an automation-focused skill, this is especially risky because users may copy these patterns into CI jobs or shared systems where secrets can be disclosed to other users or retained in audit trails.
Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.
### Permission denied
Fix:
- Change the output directory
- Elevate privileges when appropriate
- Use a writable working directory
### Multipart extraction failure