T08 · Insecure Dependencies
- Location
SKILL.md:924- Finding
Unpinned Third-Party Package Installation Creates a Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a genomics analysis tool that can produce hard-coded CNV results while presenting them as real analysis output.
Review carefully before installing or using. Do not use this skill for research, clinical, publication, or patient-related decisions until the CNV algorithm, input validation, plotting, dependency specification, and privacy handling are implemented and independently validated. Treat any current output as demonstration data only.
SKILL.md:924Unpinned Third-Party Package Installation Creates a Supply-Chain Risk
scripts/main.py:18Program Reports Fabricated CNV Results Without Reading or Validating Inputs
The skill markets itself as performing CNV calling, segmentation, and publication-quality plotting, while the document itself later admits the implementation is placeholder and planned improvements still include implementing the actual algorithm. In a genomics workflow, this can mislead users into making research or clinical-adjacent decisions based on fabricated or unsupported results, which is a serious integrity and safety risk even without classic code-execution abuse.
The skill processes and writes results derived from whole-genome data, which can contain highly sensitive patient information, but it does not give a clear operational warning near usage/output sections about handling, storage, sharing, and retention of those outputs. In this context, missing privacy guidance increases the likelihood of accidental exposure of genomic data through local files, reports, or downstream sharing.
The document uses Chinese labels in the 'Related Skills' section ('上游', '下游') while the rest of the skill is written in English, with no indication that multilingual output is intentional or user-selectable. This can violate language/locale policy when a specific language is imposed without opt-in or justification.
The security checklist claims input validation, output restriction, and sanitized errors, yet the same document states the implementation is placeholder and key functionality is not actually implemented. Security assertions without evidence can cause operators to trust the skill with sensitive genomic inputs under false assumptions, increasing the chance of improper data handling or deployment in regulated contexts.
The prerequisites state that no additional packages are required, but the troubleshooting section names external dependencies such as pysam, numpy, matplotlib, and pandas. This inconsistency is not a direct exploit primitive, but it can cause users to run ad hoc installation commands, weaken reproducibility, and undermine trust in the environment assumptions for a tool handling sensitive genomic data.