Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed media-processing skill for qhkit, with expected media uploads and dependency setup, but users should notice that it may install or update command-line software.
Install this only if you intend to use Qinghu/qhkit media processing and are comfortable with npm/Node tooling being installed or updated, providing a qhkit API token, and having selected media files uploaded for processing. Use watermark-removal features only on media you have rights to modify.
Line L03 says the skill 'must trigger' whenever a user asks to process/optimize/clean video or image materials. That scope is very broad and lacks exclusion conditions or negative examples, so it could collide with many ordinary media-related requests and cause unintended invocation.
This media-processing skill contains broad environment-bootstrapping instructions to install Node.js, npm packages, and alter runtime configuration, expanding its capability beyond the stated purpose. That increases risk because invoking the skill can lead to system modification and execution of newly downloaded software, which is unnecessary for many user requests and widens the attack surface.
The skill instructs use of npx @iqinghu/qhkit without pinning a specific version, which allows execution of whatever package version is current at invocation time. In a skill context, this creates a supply-chain risk: a compromised upstream package or newly introduced malicious release could be fetched and executed automatically on the host.
This duplicate finding points to the same persistence behavior: installing binaries under the user's home directory and adjusting PATH for reuse across commands. Even though the instructions mention checksum verification, the resulting environment modification still exceeds the least-privilege expectations for a media-editing skill and can leave long-lived changes on the host.
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 persistence behavior: installing binaries under the user's home directory and adjusting PATH for reuse across commands. Even though the instructions mention checksum verification, the resulting environment modification still exceeds the least-privilege expectations for a media-editing skill and can leave long-lived changes on the host.
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"
These lines instruct the agent to direct users to the China-site login/API-key flow and require the site to be 'cn', only preserving 'intl' if the user explicitly says they use the international account. This imposes a locale-specific workflow by default rather than offering the user a language/region choice.