港股+A股盯盘系统
PassAudited by VirusTotal on May 10, 2026.
Overview
Type: OpenClaw Skill Name: hk-stock-monitor Version: 1.0.0 The skill bundle contains hardcoded sensitive credentials, including a QVeris API key and a specific Feishu Chat ID (oc_c771930429ba9d9683b8a38fe3a9b3f9) in 'data-sources.js' and 'alert-check.js', which could lead to monitoring data being sent to the author's endpoint. Additionally, the scripts use 'execSync' with unsanitized string interpolation to call the OpenClaw CLI and external tools, introducing a high risk of shell injection. While the behavior aligns with the stated stock monitoring purpose, the combination of hardcoded secrets and insecure command execution is highly irregular for a public skill.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A malformed or maliciously edited stock name, message, API key, or code value could make the script run unintended shell commands instead of only sending a notification.
The script sends alerts by constructing a shell command from interpolated values after only limited escaping. This is purpose-aligned, but it is an unsafe pattern for a messaging tool because configurable or unexpected message content can affect shell execution.
execSync(`openclaw message send --channel feishu --target ${CONFIG.chatId} --message "${escapedMsg}"`, { encoding: 'utf-8', timeout: 30000 });Use safer process execution such as spawn/execFile with argument arrays, or call a messaging API directly; validate and escape all configurable values before use.
The skill may call a paid data provider with a credential the user did not explicitly configure, or may expose/use an embedded key whose ownership and billing impact are unclear.
The code uses a QVeris API key from the environment or falls back to a hardcoded secret-like key, while the registry metadata declares no required environment variables or primary credential.
qverisApiKey: process.env.QVERIS_API_KEY || 'sk-pQbZOXNY3p1gPIg4cXPRiM7k6_SfXpw190ZRO7ac5Gs'
Remove the hardcoded API key, declare QVERIS_API_KEY as an optional or required credential, and require explicit user configuration before any paid-provider fallback is used.
If the referenced helper is missing, changed, or compromised, the stock monitor may fail or run code outside the reviewed skill package.
The skill automatically depends on and executes a helper script from another skill path, but the manifest and install metadata do not declare that dependency or its provenance.
qverisScript: '/root/.openclaw/workspace/skills/qveris-official/scripts/qveris_tool.mjs'
Declare the qveris-official dependency and version, include reviewed helper code, or replace the shell-based helper call with a documented API integration.
Stock watchlists, alert triggers, and monitoring activity may be posted to a Feishu chat the user did not intentionally select.
The alert script contains a real-looking hardcoded Feishu target. If the user does not edit this separate file, alert messages can be sent to a preset chat destination.
chatId: 'oc_c771930429ba9d9683b8a38fe3a9b3f9'
Require the user to provide their own Feishu target, remove default chat IDs, and document every file that must be configured before alerts are enabled.
Once configured in cron, the monitor can keep running and sending alerts on a schedule until the user disables it.
The documentation suggests a recurring cron job for frequent alert checks. This is consistent with a stock-monitoring skill, but it creates ongoing background activity after setup.
*/3 9-16 * * 1-5 cd /path/to/scripts && node alert-check.js >> /var/log/alert.log 2>&1
Only add the cron jobs if you want persistent monitoring, and keep a clear uninstall or disable procedure for the scheduled tasks and generated state files.