T09 · Insecure Skill Coding Practices
- Location
ec-sample-tracker.py:419- Finding
Spreadsheet Formula Injection in CSV Exports
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent local lab sample tracker, but its import and export behavior can silently alter records or create risky spreadsheet files, so it belongs in Review rather than automatic approval.
Before installing, treat this as a local record system that can permanently change its SQLite database. Back up samples.db before imports, inspect duplicate sample_id values, prefer JSON or Markdown exports for untrusted data, and install optional dashboard dependencies only from a trusted, pinned environment.
ec-sample-tracker.py:419Spreadsheet Formula Injection in CSV Exports
ec-sample-tracker.py:493Unpinned Third-Party Dependency Installation Guidance
The bulk import path uses INSERT OR REPLACE INTO samples, which will silently overwrite any existing record with the same sample_id. In a lab sample-tracking context, this can destroy or alter provenance, status, ownership, and notes without an explicit warning, confirmation step, or audit trail, making accidental data loss or tampering materially harmful.
No suspicious patterns detected.