Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

valuescan-data-skill

v1.0.0

ValueScan数据查询Skill。支持代币搜索、K线数据、主力资金流分析、链上数据查询等加密货币市场数据分析功能。

0· 46·0 current·0 all-time
byValueScan-ai@valuescan-io
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
CryptoRequires walletCan make purchasesRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's name and description match the included endpoints and SDK: it queries crypto market and on-chain data from api.valuescan.io. However, SKILL.md and the included SDK require an API Key and Secret Key while the registry metadata reports no required credentials or config paths — a metadata mismatch that should be resolved.
Instruction Scope
SKILL.md instructs only to call the ValueScan API and perform HMAC-SHA256 signing. The included Node SDK (vs_api_sign.js) reads a credentials file from the user's home (~/.openclaw/credentials/valuescan.json) and sends requests only to https://api.valuescan.io. There are no instructions to read unrelated system files or transmit data to third‑party endpoints, but the runtime will access a user home file (not declared in registry metadata).
Install Mechanism
No install spec is provided (instruction-only), and the included code uses only Node.js built-ins (crypto/fs/fetch). No external downloads or package installs are required by the skill bundle itself.
!
Credentials
The skill legitimately requires an API key and secret for ValueScan API calls. That is proportionate to its purpose. However, the registry metadata does not declare required credentials or config paths while SKILL.md and the SDK require them and expect them in a local file (~/.openclaw/credentials/valuescan.json). This discrepancy is misleading and increases risk (user may not realize where secrets are read from).
Persistence & Privilege
always is false and the skill does not request system-wide configuration changes or persistent elevated privileges. It reads a local credential file but does not write to other skills' configs or attempt to become always-enabled.
Scan Findings in Context
[no_findings] expected: The static pre-scan reported no injection signals. The SDK code uses fs/crypto/fetch which is expected for an API client that signs requests.
What to consider before installing
This skill appears to implement a legitimate ValueScan API client, but there are important inconsistencies you should resolve before installing: - The SKILL.md and the included SDK require a ValueScan API Key and Secret and expect them in a local file: ~/.openclaw/credentials/valuescan.json. The registry metadata, however, lists no required credentials or config paths. Confirm with the publisher which credential mechanism is intended (env vars vs credential file). - If you proceed, store credentials only in a secure location (not shared accounts), and consider using separate API credentials with least privilege. Inspect the credentials file path and contents before creating it; the SDK reads this file and will throw if missing. - Review the included vs_api_sign.js yourself (it is short and uses only built-in Node modules) or request the publisher to explain the discrepancy in metadata. Verify the official dev portal (https://www.valuescan.ai/dev-portal/home/) and vet the API keys issuance process. - If you are uncomfortable storing secrets in the home credentials file, ask the publisher for an alternative (environment variables or platform secret storage) or for updated metadata that declares the required config path. If the publisher cannot explain or fix the metadata mismatch, treat the skill with caution (do not provide high-value/production credentials).
!
script/sdk/vs_api_sign.js:25
File read combined with network send (possible exfiltration).
About static analysis
These patterns were detected by automated regex scanning. They may be normal for skills that integrate with external APIs. Check the VirusTotal and OpenClaw results above for context-aware analysis.

Like a lobster shell, security has layers — review code before you run it.

latestvk975t90z99w2dskw23jekn0rtn84t38y

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments