T09 · Insecure Skill Coding Practices
- Location
SKILL.md:49- Finding
Database Credentials Exposed Through Command-Line Arguments
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This database skill is not malicious, but it needs Review because it includes high-impact backup, restore, migration, credential, and export guidance without enough scoping and safeguards.
Install only if you are comfortable supervising database operations closely. Use read-only, least-privilege credentials by default; avoid putting passwords in command lines; approve any export, backup, restore, or migration explicitly; choose protected output locations; and do not run it against production data without confirming scope and rollback plans.
SKILL.md:49Database Credentials Exposed Through Command-Line Arguments
SKILL.md:121Sensitive Database Exports and Backups Written to Predictable Shared Temporary Files
The skill claims to be read-only by default, but later sections provide direct restore and import commands that write to databases without preserving the same confirmation and transaction safeguards. This mismatch can cause an agent or operator to over-trust the skill and execute destructive changes under the assumption that the documented safety model still applies.
The backup, restore, and migration sections document operations that can overwrite data, duplicate data into other systems, or impose significant load, yet they lack strong warnings and approval requirements. These are operationally sensitive tasks where omission of safeguards makes accidental destructive changes and bulk exfiltration substantially more likely.
The early guidance encourages connecting, exploring schemas, and exporting data but does not prominently warn about sensitive data exposure such as PII, secrets, access tokens, or production records. In practice, database exploration and export are high-risk operations because even read-only access can reveal confidential information and enable large-scale data exfiltration.
The activation cues are broad enough that ordinary requests like 'check the database' or mentioning a DB name may invoke the skill prematurely. In an agent setting, over-broad triggering can lead to unnecessary connection attempts, credential requests, or execution of database inspection commands in contexts where the user did not intend database access.
The skill’s stated purpose is database exploration and querying, but the documentation also enables backup, restore, and cross-database migration. Those capabilities materially expand the blast radius from read-oriented inspection into bulk data exfiltration, overwrite, and replication operations, increasing the chance an agent uses the skill for destructive or high-impact actions the user did not clearly intend.
No suspicious patterns detected.