Security audit
Security checks for vulnerabilities and agentic risk
The skill's main data-query purpose is coherent, but it tells agents to install and upgrade runtime tooling and configure credentials with limited user control around those host changes.
Review before installing. The query behavior is understandable and includes paid-call consent, but allow installation only if you are comfortable with npm/qhkit installation, possible Node.js bootstrapping, PATH changes, and storing or providing a Qinghu API token. Prefer a preinstalled, pinned qhkit version in a controlled environment.
The trigger text includes broad language such as 'or similar needs must trigger,' which can cause the skill to activate on loosely related requests. Over-broad invocation increases the chance the agent will run this skill unnecessarily, leading to unwanted external calls, billing events, or disclosure of user-supplied identifiers to a third-party tool.
The skill includes instructions to install packages and download Node.js binaries from the network, but does not put a prominent safety gate before these system-changing actions. In an agent setting, that can lead to automatic modification of the host environment, execution of newly downloaded code, and persistence of tooling without clear user consent.
The skill instructs use of npx @iqinghu/qhkit without pinning an exact version, which makes execution depend on whatever package version is current at runtime. That creates a supply-chain risk: a compromised or breaking upstream release could be fetched and executed automatically in the user's environment.
This duplicate finding points to the same persistent-install behavior: extracting binaries into a user directory and altering PATH can outlive the session. In a skill context, such durability is risky because a data-query skill should not silently transition into host-environment modification with lasting effects.
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 persistent-install behavior: extracting binaries into a user directory and altering PATH can outlive the session. In a skill context, such durability is risky because a data-query skill should not silently transition into host-environment modification with lasting effects.
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.