Security audit
Security checks for vulnerabilities and agentic risk
This Shopee analytics skill is coherent, but it also tells the agent to install runtimes and CLI tools from the network and configure a service token during normal use.
Install only if you are comfortable with qhkit accessing Qinghu/Shopee analytics data and with the agent potentially installing Node/qhkit tooling and configuring a qhkit token. Prefer preinstalling a vetted qhkit version yourself and avoid the unpinned npx or ad hoc Node download path during normal use.
The description says the skill must trigger when the user asks the listed examples 'or提出同类需求', which broadens activation beyond the explicit phrases and leaves the boundary of matching unspecified. This can cause unintended invocation because similar everyday analytical requests may overlap without negative examples or exclusion conditions.
This is a query-oriented analytics skill, but it contains extensive instructions to install software, configure tokens, and modify the runtime environment. Expanding from data lookup into environment bootstrapping materially increases attack surface because the agent may perform privileged setup actions unrelated to the user’s immediate task.
The skill instructs use of npx @iqinghu/qhkit without pinning an exact version or integrity mechanism. That can cause execution of an unexpected package version at runtime and enlarges supply-chain risk, especially because the same skill also tells the agent to install and execute tooling from the network.
The skill directs downloading and installing Node.js from external URLs, including alternate mirror infrastructure, then using it to execute subsequent commands. Even with checksum guidance, this exceeds the declared capability and creates unnecessary remote code execution and supply-chain exposure inside the host environment.
This duplicate finding reflects the same persistence behavior: installing Node under the user's home directory and exporting a new PATH. In the context of a query skill, that is an unnecessary and dangerous state change that can influence future commands and broaden compromise impact if the downloaded toolchain is malicious or tampered with.
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 reflects the same persistence behavior: installing Node under the user's home directory and exporting a new PATH. In the context of a query skill, that is an unnecessary and dangerous state change that can influence future commands and broaden compromise impact if the downloaded toolchain is malicious or tampered with.
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 skill strongly steers users toward a specific domestic account and token flow unless they explicitly opt out. That can misdirect credential handling, create account confusion, and increase the chance that users enter secrets into the wrong service context, especially when paired with CLI configuration instructions.
No suspicious patterns detected.