Security audit
Security checks for vulnerabilities and agentic risk
The skill has a coherent Shopee brand-data purpose, but it also directs automatic software installation, updates, local persistence, and API-token configuration that users should review before use.
Install only if you are comfortable letting the skill install or update Node/npm tooling and configure a qhkit API token on the machine. Prefer preinstalling a reviewed, pinned qhkit version yourself, confirm paid-credit use before calls, and avoid giving it tokens for accounts you do not want this agent to access.
The manifest says the skill '必须触发' not only for two examples but also for '提出同类需求时', which leaves the activation boundary undefined. That ambiguity can cause unintended invocation for loosely related shopping or brand-analysis requests.
The skill goes far beyond its stated purpose of querying Shopee brand details by instructing the agent to install Node, install global packages, configure tokens, modify PATH, and bootstrap environment dependencies. This expands the attack surface from a narrow data query into arbitrary software installation and credential handling on the host, which is risky in an agent-execution setting.
The skill instructs use of npx @iqinghu/qhkit without pinning a specific version, which allows whatever the registry serves at execution time to be fetched and run. In a security-sensitive agent context, this creates a supply-chain risk and reduces reproducibility, especially because the package is used to access credentials and external services.
This duplicate finding points to the same persistence behavior: unpacking Node into a user directory and exporting a modified PATH. Even with checksum verification, the security issue is not just download integrity but the unauthorized persistence and environment mutation performed by a skill whose declared purpose is only data lookup.
cd /tmp && curl -fsSLO https://nodejs.org/dist/v22.22.3/node-v22.22.3-linux-x64.tar.xz cd /tmp && curl -fsSL https://nodejs.org/dist/v22.22.3/SHASUMS256.txt | grep ' node-v22.22.3-linux-x64.tar.xz$' | sha256sum -c - mkdir -p "$HOME/.local/lib" && tar -xJf /tmp/node-v22.22.3-linux-x64.tar.xz -C "$HOME/.local/lib" export PATH="$HOME/.local/lib/node-v22.22.3-linux-x64/bin:$PATH"
This duplicate finding points to the same persistence behavior: unpacking Node into a user directory and exporting a modified PATH. Even with checksum verification, the security issue is not just download integrity but the unauthorized persistence and environment mutation performed by a skill whose declared purpose is only data lookup.
cd /tmp && curl -fsSLO https://nodejs.org/dist/v22.22.3/node-v22.22.3-linux-x64.tar.xz cd /tmp && curl -fsSL https://nodejs.org/dist/v22.22.3/SHASUMS256.txt | grep ' node-v22.22.3-linux-x64.tar.xz$' | sha256sum -c - mkdir -p "$HOME/.local/lib" && tar -xJf /tmp/node-v22.22.3-linux-x64.tar.xz -C "$HOME/.local/lib" export PATH="$HOME/.local/lib/node-v22.22.3-linux-x64/bin:$PATH"
No suspicious patterns detected.