Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent image-generation helper, but users should understand it installs and runs external npm tooling and sends prompts/images to the qhkit service.
Install this only if you trust the qhkit npm package and the iqinghu/LinkPix service. Prompts, reference images, and the API key are used with that service, and npm/npx commands may execute externally maintained package code. Review the package source or pin versions in managed environments.
The description says requests matching this use case '必须触发' and centers the skill on Chinese-language rendering and domestic Chinese e-commerce platforms. This imposes a locale/language-specific routing requirement without any user opt-in or alternative-language choice, which is a natural-language policy concern under locale choice rules.
The skill instructs use of npx @iqinghu/qhkit without pinning an exact package version. That allows whatever version is current at execution time to be fetched and run, creating a supply-chain risk if a malicious or compromised release is published or if behavior changes unexpectedly.
This duplicated finding points to the same persistence behavior: extracting binaries into a user-owned directory and modifying PATH, potentially across future shells. Even though the text includes checksum verification, the persistence aspect remains relevant because it establishes a lasting executable foothold in the user environment.
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 duplicated finding points to the same persistence behavior: extracting binaries into a user-owned directory and modifying PATH, potentially across future shells. Even though the text includes checksum verification, the persistence aspect remains relevant because it establishes a lasting executable foothold in the user environment.
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 falls back to npx --yes sharp-cli without a pinned version, which executes code fetched at runtime from the package registry. This introduces a similar supply-chain exposure: an attacker controlling or compromising a package release could gain code execution in the agent environment.