Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed image watermark-removal integration that uses an external Qinghu/qhkit service, with some normal installation and credential risks users should understand.
Install only if you are comfortable using the Qinghu/qhkit service, providing its API token, uploading the target image to that service, and installing npm/Node tooling. Confirm the estimate before generation because credits may be charged, and use the skill only on images you own or are authorized to modify.
The description says the skill 'must trigger' whenever a user wants to remove watermarks, logos, text, or marks from an image, and then lists broad keyword-style terms. While domain-related, these activation conditions are not bounded by explicit exclusions or negative examples, which could cause unintended invocation for adjacent image-editing requests.
The skill instructs use of npx @iqinghu/qhkit without pinning a specific version, which allows execution of whatever package version is current at install time. That creates supply-chain risk: a malicious or compromised future release could be fetched and run automatically in the agent environment.
This duplicate finding points to the same behavior: unpacking downloaded binaries into a user-controlled persistent directory and exporting that location into PATH. Even though the text recommends checksum verification, the persistence aspect still leaves additional software resident for future execution contexts.
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 downloaded binaries into a user-controlled persistent directory and exporting that location into PATH. Even though the text recommends checksum verification, the persistence aspect still leaves additional software resident for future execution contexts.
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 '何时触发' section provides a few positive examples but does not define boundaries for when the skill should not be invoked. Without exclusions or a complete trigger scope, similar everyday requests about editing images or removing text could overlap and activate the skill unintentionally.