T08 · Insecure Dependencies
- Location
SKILL.md:46- Finding
Mutable Remote Package Execution During Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This fertility tracking skill matches its general purpose, but it handles highly sensitive health data with misleading privacy claims, automatic partner-email behavior, plaintext storage, and unpinned install instructions.
Install only after reviewing the code and configuration carefully. Treat the Oura token, cycle history, symptoms, LH results, and partner email settings as highly sensitive; avoid enabling partner/email alerts unless every recipient has explicitly consented, store secrets outside shared or backed-up folders, and do not rely on predictions as medical advice or contraception guidance.
SKILL.md:46Mutable Remote Package Execution During Installation
v2/index.js:306Sensitive Reproductive Health Records Stored as Unencrypted JSON
config.example.txt:5Reusable Email Credential Stored in Plaintext Configuration
The skill claims broad multi-signal fusion and learning, but the finding suggests narrower temperature-centric logic and only partial LH usage. This discrepancy is especially concerning in a reproductive-health skill because inaccurate user expectations can drive unsafe reliance and unnecessary disclosure of sensitive data.
The skill claims broad multi-signal fusion and learning, but the finding suggests narrower temperature-centric logic and only partial LH usage. This discrepancy is especially concerning in a reproductive-health skill because inaccurate user expectations can drive unsafe reliance and unnecessary disclosure of sensitive data.
The skill claims broad multi-signal fusion and learning, but the finding suggests narrower temperature-centric logic and only partial LH usage. This discrepancy is especially concerning in a reproductive-health skill because inaccurate user expectations can drive unsafe reliance and unnecessary disclosure of sensitive data.
The skill claims broad multi-signal fusion and learning, but the finding suggests narrower temperature-centric logic and only partial LH usage. This discrepancy is especially concerning in a reproductive-health skill because inaccurate user expectations can drive unsafe reliance and unnecessary disclosure of sensitive data.
The privacy section says data never leaves the user's machine, yet elsewhere the skill documents partner email alerts, which necessarily transmit sensitive fertility information externally. False privacy assurances around reproductive health data can cause users to enable features they would otherwise reject, resulting in unauthorized disclosure.
The skill transmits sensitive health data to the Oura API using an authorization token, but the file shows no user-facing disclosure, consent flow, or minimization controls. Because fertility and readiness data are highly sensitive, undisclosed external transmission can expose intimate health information and create compliance and privacy risks.
These emails contain explicit fertility status, ovulation timing, and sexual activity recommendations, which are highly sensitive medical and reproductive data. Sending them without explicit warning, confirmation, and privacy safeguards risks disclosure to unintended recipients through shared mailboxes, forwarding, or account compromise.
The health-status alert emails disclose inferred illness or severe stress indicators derived from wearable data without prior disclosure or confirmation. Such unsolicited transmission of sensitive health assessments can cause privacy harm and may expose medical inferences to anyone with access to the email account.
The README promotes fertility and ovulation predictions with quantified accuracy claims and personalized learning, but it does not prominently warn that the tool is not medical advice and should not be used as the sole basis for health, conception, or contraception decisions. In this context, users may rely on the predictions for reproductive or medical decisions, creating meaningful risk of harm from false confidence, delayed care, or unintended pregnancy.
The configuration example includes partner email alerts and automated daily checks for highly sensitive reproductive data, but it does not clearly warn users that intimate fertility information may be transmitted to another person or over external channels. Because fertility status, symptoms, and cycle predictions are sensitive health-related data, accidental or uninformed disclosure can cause privacy harm, relationship harm, or coercive misuse.
This code produces ovulation predictions and confidence values from highly sensitive reproductive health signals, but it contains no guardrails, uncertainty messaging, or indication that outputs are not medical advice. In a fertility-tracking context, users may reasonably rely on these predictions for conception or pregnancy-avoidance decisions, so inaccurate or overconfident output can cause significant real-world harm.
The prediction logic returns actionable, confident-sounding fertility guidance such as 'Optimal TTC timing' and likely ovulation windows without any warning that the output is probabilistic, fallible, and unsuitable as a sole basis for contraception or conception planning. Because this is a reproductive-health use case, omission of uncertainty and safety disclaimers materially increases the risk of harmful real-world decisions, including unintended pregnancy or delayed care.
The changelog claims the feature was 'tested with real user data' but gives no indication that consent, de-identification, retention limits, or privacy protections were in place. Because the skill handles reproductive and health-related signals, use of real user data without documented safeguards raises serious privacy and compliance concerns and may normalize unsafe data practices.
The changelog describes automated partner email alerts and timing guidance tied to LH surge and fertility status, but provides no indication of explicit consent, recipient verification, opt-in controls, or warnings about sharing highly sensitive reproductive health data. In a fertility-tracking context, this can expose intimate medical information to third parties, creating substantial privacy, safety, and relationship-abuse risks if misconfigured or enabled without clear user approval.
The feature list states 'LH test strip analysis: Photo-based progression tracking' as an available capability. However, the roadmap and contributing sections explicitly list 'LH strip image recognition' as future work, which contradicts the earlier claim that the agent currently analyzes strip photos.
The README understates or omits clear warnings that highly sensitive reproductive health data may be shared with third-party services like Oura, Open-Meteo, SMTP providers, and with a partner via email notifications. Because fertility status and cycle data are especially sensitive, inadequate disclosure can lead to privacy harm, unintended disclosure, and compliance issues.
The README instructs users to store a long-lived Oura access token in a plaintext file under the home directory, which increases the chance of credential theft through local compromise, backups, logs, or overly broad file permissions. Since this token grants access to health-related wearable data, compromise can expose sensitive biometric and cycle information.
https://cloud.ouraring.com/personal-access-tokens
echo "YOUR_TOKEN_HERE" > ~/.config/oura/token.txt
The trigger phrase 'My period started today' is natural language that could easily appear in ordinary conversation, journaling, or health discussions, causing unintended activation. In this skill, accidental invocation is more sensitive because it can initiate fertility tracking workflows and partner notifications involving intimate health data.
The LH Testing Protocol tells users 'Agent analyzes and tracks progression' after they send a strip photo. Elsewhere, the document lists LH strip image recognition as a not-yet-built feature, so this operational instruction overstates what the skill currently does.
The skill documents capabilities that require network access and local secret/config handling, but it declares no explicit tool scope or permissions. In a health-related skill handling reproductive data, missing permission boundaries increases the chance of overbroad access, hidden exfiltration, or unsafe execution by an agent runtime.
Using npx clawhub@latest install fertility-tracker relies on a moving package version, which can change over time and pull unreviewed code into the installation path. This creates a supply-chain risk where a compromised or malicious upstream release could execute during install.
The configuration stores an Oura API token and partner email settings, but the documentation does not clearly warn users that the skill accesses sensitive health data and may transmit it through integrations. Inadequate disclosure around secret handling and health-data sharing creates elevated privacy and account-security risk.
The skill describes automatic partner email alerts for LH surge and ovulation timing without a clear privacy warning or consent framing. These messages contain highly sensitive reproductive health information, and automatic transmission can expose intimate data through inbox compromise, shared accounts, forwarding, or mistaken recipients.
Claiming that all analysis happens locally conflicts with documented use of the Oura API, which requires external data exchange. Even if computation is local after retrieval, the statement is materially misleading about the privacy model and third-party exposure.
The repeated npx clawhub@latest command again exposes users to unpinned remote code execution during installation. Repetition in prominent call-to-action sections increases the chance that users will follow the unsafe path without review.