Skill flagged — suspicious patterns detected

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

Panda Data Skill

v1.0.0

PandaAI 金融数据 API 的 LLM Tool 封装,35 个数据查询方法,支持行情、财务、期货等

0· 110·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
Skill name/description match the provided tools and code (financial data API wrapper). However the runtime documentation and script require the panda_tools package and environment credentials (SKILL.md instructs to set PANDA_DATA_USERNAME and PANDA_DATA_PASSWORD and to install a local wheel), while the registry metadata declares no required env vars or install steps. This mismatch is unexpected and reduces trust in the metadata.
Instruction Scope
SKILL.md and scripts constrain behavior to initializing credentials and calling PandaAI tools (ToolRegistry/Tool call patterns). There are no instructions to read unrelated files or exfiltrate data. Still, instructions give the agent broad freedom to call any of 35 tools and expect credentials to be loaded from the environment (via CredentialManager.init_from_env()), so inspecting what CredentialManager reads/does is important.
Install Mechanism
There is no automated install spec (instruction-only + a small helper script). That minimizes install-time risk because nothing is downloaded by the skill itself. However SKILL.md requires the user to install a local wheel (panda_data / panda_tools) outside the registry; the origin and integrity of that wheel must be verified by the user.
!
Credentials
The skill logically requires API credentials (username/password) to access the PandaAI data API; this is proportionate to the stated purpose. The problem is those required env vars are not declared in the registry metadata (required env vars: none). This omission is a red flag: the runtime will read credentials from the environment but the package listing does not advertise that requirement. Also, CredentialManager.init_from_env() could read other env variables or behave differently than documented — review its implementation before supplying high-privilege secrets.
Persistence & Privilege
Skill does not request always:true, does not modify other skills or system settings, and contains no install-time persistence. It only provides a helper CLI script that calls the declared ToolRegistry functions.
What to consider before installing
Key things to check before installing or using this skill: - Metadata mismatch: SKILL.md says you must set PANDA_DATA_USERNAME and PANDA_DATA_PASSWORD and install a local panda_data/panda_tools wheel, but the registry metadata lists no required env vars or install steps. Ask the publisher to fix the metadata or document this clearly. - Verify package origin: the README/homepage points to a GitHub repo. Download and inspect the panda_tools / panda_data package source (or wheel) from that repo before installing. Prefer installing from an official release tarball or GitHub release with checksums. - Inspect CredentialManager: review the implementation of CredentialManager.init_from_env() in the panda_tools package to confirm which environment variables it reads and how it uses/transmits credentials (e.g., ensure it only sends credentials to PandaAI endpoints and does not log or post them elsewhere). - Least privilege: create a dedicated API account with minimal permissions for this skill rather than reusing high-privilege credentials. - Run in isolation: until verified, run the skill in a sandboxed environment (container/VM) and avoid exposing other credentials or sensitive data in the environment. - If you need registry transparency: request that the skill author update the registry metadata to declare required env vars and any install requirements so automated vetting and users are not surprised. These steps will reduce risk and clarify whether the credential handling and package provenance are trustworthy.

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

latestvk9735mr49xvej907rmmjcgqgxs83h1p3

License

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

Comments