T08 · Insecure Dependencies
- Location
scripts/install.sh:24- Finding
Unpinned Global npm Package Is Installed and Immediately Executed
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This mood-analysis skill appears purpose-built, but it relies on unreviewed globally installed code and broad triggers that could send sensitive mood text to an external service unexpectedly.
Review this carefully before installing. Only install if you are comfortable with a global npm package running on your machine, using a DeepSeek API key, and potentially sending mood-related text to DeepSeek. Prefer a pinned, locally installed, fully reviewed CLI implementation, restrict the API-key file permissions, and avoid submitting highly sensitive personal or mental-health details until privacy and retention behavior are clearer.
scripts/install.sh:24Unpinned Global npm Package Is Installed and Immediately Executed
scripts/install.sh:37API-Key Configuration File Is Created Without Restrictive Permissions
The skill description says it analyzes mood via a CLI tool but does not warn that the text may be sent to an external API service using DEEPSEEK_API_KEY. For a mood-analysis skill, the input is likely to contain sensitive emotional or mental-health-adjacent data, so omission of this disclosure undermines informed consent and increases privacy risk.
The changelog states the skill supports natural-language triggering via broad keywords such as “mood”, “心情”, and “情绪”, which are generic terms likely to appear in ordinary conversation. Overly broad activation criteria can cause unintended skill invocation, sending user text to the mood-analysis CLI or downstream LLM when the user did not explicitly request that action, creating privacy and routing risks.
The README states that mood text is analyzed by an external AI service (DeepSeek) but does not clearly warn users that their potentially sensitive emotional disclosures will be transmitted off-device. Because mood and mental-state text can contain highly personal information, the lack of an explicit privacy/data-transfer notice may cause users to disclose sensitive content without informed consent.
The README advertises automatic saving of analysis history and future emotion statistics/reporting, but it does not warn users that sensitive mood-analysis results may be stored locally. Local persistence of emotional data can expose private information to other local users, backups, malware, or accidental disclosure if retention behavior is not clearly explained.
The trigger list includes broad everyday phrases like '心情怎么样' and '心情好吗' that can easily appear in normal conversation, causing the skill to activate when the user did not clearly intend to invoke an external mood-analysis tool. In this skill, unintended activation is more dangerous because the analyzed text may be sent to a third-party API handling sensitive emotional content.
Keyword-based activation on generic phrases such as '分析情绪', '今天心情', and '心情好/不好' is overly permissive and can match ordinary chat content. Because the skill is designed to process free-form user text and may forward it to DeepSeek, accidental activation can expose sensitive personal content without a deliberate user action.
The planned history, statistics, report, and batch-analysis features describe retaining emotional inputs and analysis results over time without defining retention limits, minimization, access controls, or user consent boundaries. Emotional self-expression is sensitive data, so persistent storage materially increases privacy harm if the host, logs, or exported reports are accessed by others.
The best-practice guidance recommends logging every invocation result, which in this skill can include highly sensitive user emotional text, inferred mood labels, and confidence values. Centralized logs often have broader retention and wider operator access than application data, so this creates avoidable secondary exposure of sensitive information.
The script performs npm install -g mood-weather-cli, which installs executable code system-wide and places a new command on the user's PATH. Global package installation increases blast radius if the package is compromised, typosquatted, or later updated maliciously, and it exceeds the least-privilege model for a narrowly scoped sentiment-analysis skill.
The install script introduces and operationalizes a remote DeepSeek API dependency by creating an API-key config and running a health check, while the skill description only presents local mood analysis via a CLI. This mismatch matters because user text may be sent to a third-party service without clear disclosure, expanding the data exposure and trust boundary beyond what users would reasonably expect.
The script creates a plaintext environment file intended to hold a live API key but does not set restrictive permissions or clearly warn that sensitive credentials will be stored unencrypted on disk. On multi-user or backed-up systems, this can lead to accidental credential exposure through permissive file modes, logs, sync tools, or user mishandling.
Several trigger patterns are broad natural-language phrases such as "my mood", "心情怎么样", and "how am I feeling", which can easily appear in ordinary conversation without the user intending to invoke a CLI-backed skill. Because the skill uses extractArg: true and executes the mood command, ambiguous activation expands the attack surface for accidental or adversarial prompt routing.
The help trigger includes the generic phrase "帮助", which is a common everyday word and can invoke this skill unintentionally in many unrelated conversations. In an agent environment, broad triggers increase the chance of accidental command execution and misrouting user intent, especially because this skill launches executable commands for help output.
Most of the skill's user-facing instructions and examples are in Chinese, while the document does not state that the skill is intended only for Chinese-speaking users or offer an explicit language option. This can amount to an implicit language policy restriction without user opt-in.
The package description is written entirely in Chinese, which can constitute a language/locale policy issue when no alternative language option or opt-in is provided. In this manifest, there is no indication that the skill is intentionally region-specific or that users can choose another language.
Using a caret range for node-fetch allows future installs to resolve to different patch/minor versions, which weakens supply-chain reproducibility and makes security posture harder to verify. In a CLI skill that may process user input and perform network requests, dependency drift can unexpectedly introduce vulnerable or malicious code.
"node": ">=14.0.0"
},
"dependencies": {
"node-fetch": "^2.6.9",
"commander": "^9.4.0",
"dotenv": "^16.0.3",
"axios": "^1.4.0"
The manifest references node-fetch with a non-exact version while known advisories exist for some node-fetch releases, so the actual installed package may be affected and cannot be reliably verified from this file alone. Because this CLI likely performs outbound HTTP requests, issues involving header forwarding or redirect handling could expose tokens or sensitive request metadata in certain configurations.
Using an unpinned commander version reduces build determinism and increases supply-chain risk because different environments may install different releases over time. While commander itself is a common CLI library, version ranges still make it harder to attest what code is actually executed.
},
"dependencies": {
"node-fetch": "^2.6.9",
"commander": "^9.4.0",
"dotenv": "^16.0.3",
"axios": "^1.4.0"
}
An unpinned dotenv dependency permits dependency drift, which can undermine reproducibility and make incident response or vulnerability verification harder. Because dotenv influences runtime configuration loading, unexpected package changes could affect secret handling behavior.
"dependencies": {
"node-fetch": "^2.6.9",
"commander": "^9.4.0",
"dotenv": "^16.0.3",
"axios": "^1.4.0"
}
}
Using a caret range for axios is a supply-chain risk and is more significant here because axios is a network-facing HTTP client commonly implicated in SSRF, redirect, and request-handling issues. In a sentiment-analysis CLI that likely calls external APIs, an unexpected resolved version could materially affect network security behavior.
"node-fetch": "^2.6.9",
"commander": "^9.4.0",
"dotenv": "^16.0.3",
"axios": "^1.4.0"
}
}
Axios has a history of multiple security advisories, and the manifest does not pin an exact version, so the deployed package may resolve to an affected release without easy verification. This is more concerning in a CLI skill that likely sends user text to remote services, where SSRF, proxy bypass, or request-manipulation flaws could impact confidentiality or network boundary controls.
Comments, status messages, and usage text are presented only in Chinese, which imposes a specific language on users without opt-in or alternative locale support. This is a natural-language policy concern because the skill does not offer any language selection or document a justified locale restriction.
The manifest presents the skill description in Chinese, and the output prefix is also fixed in Chinese, while the trigger set includes English phrases. This suggests the skill may respond in a specific language without offering user opt-in or documenting a locale-specific scope.
The output prefix and several help-related strings are hardcoded in Chinese, but the manifest also accepts English triggers like "analyze mood" and "how am I feeling". This creates a natural-language policy concern because users invoking the skill in English are not given a language choice or notice of the forced locale.