Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed connector for paid Qinghu Shopee category data, with the main risks being setup of qhkit/Node, token configuration, and paid API calls.
Before installing, confirm you are comfortable installing qhkit/Node from the disclosed sources and providing a Qinghu API token. Approve paid qhkit calls only when the requested Shopee site, date, level, and estimated charge are clear; using a preinstalled or pinned qhkit version would reduce supply-chain uncertainty.
The description says similar requests 'must trigger' and includes broad keywords, making invocation boundaries loose. Over-broad activation can cause the agent to invoke this paid external tool in contexts where it is unnecessary, leading to unintended data disclosure, needless external calls, or unauthorized charges.
The skill exceeds its stated data-query purpose by directing installation of Node/qhkit, persistent PATH changes, and API token configuration on the host. This materially increases attack surface and can lead an agent to modify the environment, introduce new software, and handle secrets, all of which are risky in a skill that should be limited to querying category data.
The skill instructs use of npx @iqinghu/qhkit without pinning an exact version, which allows whatever version is current at execution time to be fetched and run. That creates supply-chain risk and undermines reproducibility, especially because the fetched package is then used to access external services and credentials.
This duplicate finding identifies the same persistence behavior: unpacking Node into the user's home directory and exporting a new binary path. In the skill context, that is unnecessarily invasive and increases long-term trust in newly downloaded binaries, which is disproportionate to a simple data-retrieval function.
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 identifies the same persistence behavior: unpacking Node into the user's home directory and exporting a new binary path. In the skill context, that is unnecessarily invasive and increases long-term trust in newly downloaded binaries, which is disproportionate to a simple data-retrieval function.
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"
The example trigger '各类目的销量对比' is generic and could refer to many contexts, sites, platforms, or datasets beyond this specific Shopee site-level category tool. Without requiring Shopee, site, level, or dataset context in the trigger guidance, it risks unintended activation.
No suspicious patterns detected.