T09 · Insecure Skill Coding Practices
- Location
audit.py:218- Finding
High-Risk Executables Can Be Misclassified as Safe When Decoy Source Code Is Present
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a disclosed local security checker, but its scanner can incorrectly label risky packages as safe, so it needs review before installation.
Install only if you treat it as a lightweight helper, not as a trust gate. A clean result should not be used as proof that downloaded code is safe, especially when binaries, scripts, obfuscated strings, or unreadable files are present. Run it only on directories you intend to disclose to the scanner, and avoid --output paths that could overwrite important files.
audit.py:218High-Risk Executables Can Be Misclassified as Safe When Decoy Source Code Is Present
audit.py:94Destructive String Removal Allows Embedded Payloads to Evade Pattern Detection
audit.py:109Suppressed Scan Exceptions Cause Incomplete Audits to Be Reported as Clean
The skill documents workflows that read from and write reports to the filesystem, but it does not declare any explicit tool scope such as permissions or allowed-tools. In an agent environment, undeclared file capabilities weaken policy enforcement and make it harder to constrain or review what the skill may access, especially because this skill is intended to inspect untrusted external resources.
The README contains the Chinese term "疑似" inside an example output line, introducing a language/locale inconsistency in user-facing content. The file does not offer language selection or explain that mixed-language output is intentional or region-specific, which can violate language-consistency policy expectations.
This code performs a file write based on user input via --output, but the write path has no confirmation prompt and no nearby user-facing disclosure that an existing file may be overwritten. Although saving a report is part of the tool's function, the code itself does not warn about this potentially data-affecting operation.
Detected: suspicious.dynamic_code_execution