T08 · Insecure Dependencies
- Location
README.md:17- Finding
Mutable Package Execution Through an Unpinned npx Installation Command
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is not malicious, but it needs review because it stores sensitive medication history and Discord identifiers and can write unclear messages into the medication log.
Install only if you are comfortable with a local plaintext medication log containing Discord identifiers, and prefer a pinned installer version. Before using it for real medication tracking, add code-side rejection of unknown events, sanitize CSV fields before spreadsheet use, and define retention/deletion and file-permission practices for the log.
README.md:17Mutable Package Execution Through an Unpinned npx Installation Command
scripts/tracker_v2.py:201Unrecognized Messages Are Persisted as Medication History
scripts/tracker_v2.py:73Spreadsheet Formula Injection Through Unsanitized CSV Fields
The README instructs users to install and execute clawhub via npx ...@latest, which pulls the newest published package rather than a reviewed, pinned version. If the upstream package is compromised or a breaking/malicious release is published, users following the documentation could execute attacker-controlled code on their system during installation or skill setup.
The README explicitly documents persistent logging of medication events, timestamps, and source identifiers to a CSV file, but does not warn users that this is sensitive health data. In this skill context, the data is especially privacy-sensitive because it can reveal medical conditions, treatment adherence, and user identity linkage via Discord metadata; lacking disclosure increases the risk of accidental retention, insecure storage, or sharing.
The skill uses environment variables and reads/writes persistent local files, but it does not declare an explicit tool scope such as permissions or allowed-tools. That creates an authorization ambiguity where a host may grant broader capabilities than reviewers or users expect, increasing the risk of unintended file access or persistent data modification. In this case, the skill is designed to log medication data locally, so the behavior is contextually relevant, but the undeclared scope still weakens least-privilege controls around sensitive health-related data.
The README explicitly documents that the skill stores sensitive health-related medication events together with Discord identifiers in a CSV file, but it provides no privacy, retention, access-control, or handling guidance. In the context of medication tracking, this creates a real confidentiality risk because operators may deploy the skill without understanding that it persists regulated or highly sensitive personal data linked to identifiable users.
Data from a source is assigned to a variable that is later passed to a sink, creating a variable-mediated taint flow.
def initialize_logs() -> None:
ensure_dirs()
if not os.path.exists(STRUCTURED_LOG_FILE):
with open(STRUCTURED_LOG_FILE, "w", newline="", encoding="utf-8") as f:
writer = csv.DictWriter(f, fieldnames=CSV_FIELDS)
writer.writeheader()
The script persistently stores sensitive health data together with source channel, message, and author identifiers in a plaintext CSV on disk. In the context of a medication-tracking skill, this is especially sensitive because it creates a durable record of medication behavior and user-linked metadata without any retention controls, minimization, encryption, or explicit consent handling in code.
Data from a source is assigned to a variable that is later passed to a sink, creating a variable-mediated taint flow.
def append_structured_row(row: dict) -> None:
initialize_logs()
with open(STRUCTURED_LOG_FILE, "a", newline="", encoding="utf-8") as f:
writer = csv.DictWriter(f, fieldnames=CSV_FIELDS)
writer.writerow(row)