T08 · Insecure Dependencies
- Location
SKILL.md:39- Finding
Unpinned Third-Party Package Is Downloaded and Executed via npx
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The reviewed local code is a coherent cryptocurrency price CLI, but the install instructions tell users to run an unpinned remote npm package that does not clearly match the reviewed package identity.
Review before installing. The local scripts appear limited to CoinGecko price queries and local alert-rule storage, but do not run the documented npx command unless it is pinned to a reviewed version and the npm package identity is verified against these artifacts. Expect network calls to CoinGecko and manual, not continuous, alert checks.
SKILL.md:39Unpinned Third-Party Package Is Downloaded and Executed via npx
Referenced artifact was not completely inspected
node scripts/watch.mjs btc
Referenced artifact was not completely inspected
node scripts/watch.mjs btc
Referenced artifact was not completely inspected
node scripts/watch.mjs btc
Referenced artifact was not completely inspected
node scripts/alert.mjs btc --above 100000
Referenced artifact was not completely inspected
node scripts/alert.mjs btc --above 100000
Referenced artifact was not completely inspected
node scripts/alert.mjs btc --above 100000
The README instructs users to run npx @gztanht/cryptowatch without pinning a specific version. This makes execution dependent on whatever package version is currently published, creating a supply-chain risk where a compromised or malicious update could be fetched and executed immediately by users.
The skill advertises network-dependent functionality via CoinGecko and Node/NPM usage, but it does not declare an explicit tool scope such as allowed network access. Missing scope metadata weakens the trust boundary for an agent platform because reviewers and runtime policy engines cannot clearly determine what external capabilities the skill is expected to use.
The manifest description and the main usage/documentation content are presented in Chinese, and the file does not indicate that users may choose another language. This can violate a language/locale policy when a skill implicitly forces one language for all users without opt-in or justification.
Using 'npx @gztanht/cryptowatch' without pinning a version causes the latest published package to be fetched and executed at runtime. This creates a supply-chain risk: if the package is updated maliciously, compromised, or a breaking version is released, users may execute unreviewed code with network and local environment access.
The script presents its description, help, errors, and status messages entirely in Chinese, which forces a specific language experience. The policy only permits this when the skill offers language choice or clearly documents and justifies the locale restriction, which is not present here.
The manifest describes '实时监控' and '价格突破自动预警', implying continuous monitoring with automatic alerting. In reality, the code merely saves alert definitions to a local JSON file and only checks prices when the script is explicitly run; it even states that checks must be run manually or via cron.
This code presents its title, help text, status messages, and errors in Chinese, which imposes a specific language on all users. The policy allows locale constraints only when justified or when users can opt in, neither of which is present here.
The top-of-file documentation states '实时价格监控' (real-time price monitoring), which implies ongoing observation. In practice, the script makes a single API request, prints output, and terminates, so the documentation overstates what the code does.
This file contains natural-language descriptions, help output, and runtime messages in Chinese only, including the header and command help. Under the policy, forcing a specific language without user opt-in is a locale/language policy violation unless the skill is clearly documented as region-specific, which is not evident here.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import fetch from 'node-fetch';
const API = 'https://api.coingecko.com/api/v3';
// 配置
const DEFAULT_COINS = ['bitcoin', 'ethereum', 'solana', 'bnb', 'xrp', 'dogecoin', 'cardano', 'avalanche-2'];
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import fetch from 'node-fetch';
const API = 'https://api.coingecko.com/api/v3';
// 配置
const DEFAULT_COINS = ['bitcoin', 'ethereum', 'solana', 'bnb', 'xrp', 'dogecoin', 'cardano', 'avalanche-2'];
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import fetch from 'node-fetch';
const API = 'https://api.coingecko.com/api/v3';
// 配置
const DEFAULT_COINS = ['bitcoin', 'ethereum', 'solana', 'bnb', 'xrp', 'dogecoin', 'cardano', 'avalanche-2'];
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import fetch from 'node-fetch';
const API = 'https://api.coingecko.com/api/v3';
// 配置
const DEFAULT_COINS = ['bitcoin', 'ethereum', 'solana', 'bnb', 'xrp', 'dogecoin', 'cardano', 'avalanche-2'];
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import fetch from 'node-fetch';
const API = 'https://api.coingecko.com/api/v3';
// 配置
const DEFAULT_COINS = ['bitcoin', 'ethereum', 'solana', 'bnb', 'xrp', 'dogecoin', 'cardano', 'avalanche-2'];
The manifest describes '实时监控加密货币价格,价格突破自动预警' (real-time monitoring with automatic alerts on threshold breaks). However, the implementation is a CLI that fetches current prices or market rankings once per invocation and exits; there is no continuous monitoring loop, no threshold configuration, and no alerting behavior.
This markdown file documents that the skill fetches live cryptocurrency data from the CoinGecko API, but it does not warn users that running the skill will make outbound network requests. For markdown files, SQP-2 applies when the skill description omits warnings about behaviors that could affect privacy or system integrity; even if low risk, external network access should be disclosed.
The natural-language description is written in Chinese only, which can impose a language expectation on users without any opt-in or alternative locale indicated. Under the stated policy, forcing a specific language without user choice is a natural-language policy concern.
The dependency is specified with a caret range (^3.3.2), which allows future compatible releases to be installed implicitly. This weakens supply-chain predictability and can cause the skill to pick up vulnerable or malicious dependency updates without explicit review, especially because the package performs network-related functionality.
"author": "@gztanht",
"license": "MIT",
"dependencies": {
"node-fetch": "^3.3.2"
},
"repository": {
"type": "git",
The manifest references node-fetch without exact pinning, while known advisories exist for some node-fetch releases. Because the installed version is not fully constrained here, consumers may resolve to an affected release or remain unable to verify whether the dependency is safe, creating avoidable supply-chain and network-request risk.