Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed Shopee keyword lookup skill that uses Qinghu's paid qhkit tool, with setup and token requirements that are visible and aligned with its purpose.
Install this only if you are comfortable using Qinghu's qhkit package, providing a Qinghu API token, and sending Shopee keyword queries to that external service. Before any paid lookup, confirm the Shopee site, billing period, keywords, and estimated credit cost; avoid letting the generic phrase "关键词详情" trigger paid calls for non-Shopee requests.
The trigger text says the skill 'must' activate for broad, loosely defined similar requests, which can cause over-invocation of a paid external tool and unnecessary collection/transmission of user data. In agent settings, broad triggers are dangerous because they reduce user intent verification and make accidental tool use more likely.
The invocation examples include the generic phrase '关键词详情', which lacks scope constraints and may match unrelated keyword-analysis requests outside Shopee or outside this specific tool's capability. In context, that increases the risk of incorrect tool activation, unintended paid calls, and data being sent to an external service without sufficiently specific user intent.
The skill instructs use of npx @iqinghu/qhkit without pinning a specific version, which makes execution dependent on whatever package version is current at runtime. That creates supply-chain and reproducibility risk: a malicious or compromised future release could be pulled automatically, and behavior may change unexpectedly across sessions.
This is a duplicate detection of the same persistence behavior: extracting Node into a user-controlled directory and exporting a modified PATH. The context makes it somewhat less severe than outright shell-profile persistence because it states the PATH change is shell-local, but it still normalizes environment bootstrapping and durable binary placement as part of routine tool execution.
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 is a duplicate detection of the same persistence behavior: extracting Node into a user-controlled directory and exporting a modified PATH. The context makes it somewhat less severe than outright shell-profile persistence because it states the PATH change is shell-local, but it still normalizes environment bootstrapping and durable binary placement as part of routine tool execution.
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.