Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent image-design helper that uses the qhkit service, with ordinary dependency and account-token setup risks disclosed in the instructions.
Before installing, confirm you are comfortable letting the agent install or update qhkit/Node, store or use a qhkit token, upload the selected design image to the qhkit service, and spend account credits. Prefer a reviewed or pinned qhkit version if your environment has stricter supply-chain requirements.
The description says the skill 'must trigger' for broad classes of common design requests, which can cause unintended invocation and expand the number of contexts where the skill gains influence over execution. In this skill, that matters because it also contains installation, configuration, and external service usage guidance, so overbroad triggering increases exposure to those risky behaviors.
The skill recommends executing npx @iqinghu/qhkit without pinning a specific version, which allows whatever package version is currently published to be fetched and executed at runtime. That creates a supply-chain risk: a compromised upstream package or malicious newly published version could run arbitrary code in the agent environment.
This duplicate finding points to the same behavior: extracting Node into a user-controlled directory and prepending it to PATH. That is risky because it persists tooling in the user environment and can influence later commands, increasing the blast radius if the installed runtime or subsequent packages are compromised.
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 behavior: extracting Node into a user-controlled directory and prepending it to PATH. That is risky because it persists tooling in the user environment and can influence later commands, increasing the blast radius if the installed runtime or subsequent packages are compromised.
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 instructions require use of the China-site iqinghu.com flow and explicitly direct the operator not to guide users to the international site unless the user clearly says they use it. This imposes a locale-specific workflow by default without offering a neutral language/locale choice or opt-in.