Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed image-generation workflow that installs and configures the expected qhkit CLI, with ordinary dependency and API-token risks users should understand.
Install only if you are comfortable giving qhkit an API key, uploading product/reference images to the service, and letting the agent install Node/npm tooling or image-compression dependencies. Prefer pinned package versions or preinstalled trusted tooling in managed environments.
The skill instructs use of npx @iqinghu/qhkit without pinning a specific 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. In this skill, that risk is heightened because the fetched CLI is then used to handle API tokens and submit remote jobs.
This duplicate finding points to the same behavior: unpacking Node under the user's home directory and exporting a new PATH, with guidance to make it persistent across shells. Even though the binary is checksum-verified, the persistence itself is the issue because it leaves long-lived tooling on the system and alters command resolution for future sessions. In the context of an agent skill, persistent environment mutation is more dangerous than in ordinary documentation because it can affect unrelated later tasks.
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: unpacking Node under the user's home directory and exporting a new PATH, with guidance to make it persistent across shells. Even though the binary is checksum-verified, the persistence itself is the issue because it leaves long-lived tooling on the system and alters command resolution for future sessions. In the context of an agent skill, persistent environment mutation is more dangerous than in ordinary documentation because it can affect unrelated later tasks.
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 will download and execute the latest package version at runtime. This is a classic supply-chain exposure: if the package or one of its dependencies is compromised, arbitrary code may execute in the agent environment. The danger is increased here because this path is presented as an automatic remediation step for oversized user-supplied images.