Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Douyin video-generation helper that installs and uses the qhkit CLI, but users should understand the API key, package-install, and credit-spending implications before use.
Install only if you are comfortable using the qhkit/iqinghu service, providing its API key to configure the CLI, uploading source media to that service, and spending account credits after explicit confirmation. Prefer a pinned qhkit version in controlled environments and avoid persisting PATH changes unless you want this tool available across sessions.
The description says the skill 'must trigger' for a wide class of Douyin-related requests, effectively forcing invocation based on broad topic keywords rather than precise task fit. In this skill's context, that is riskier because invocation can lead to installation steps, token collection guidance, and external CLI execution, amplifying the consequences of false activations.
The activation guidance uses broad marketing-oriented trigger phrases such as generic requests for Douyin promotional videos, which can cause the skill to activate in situations where a more specific or safer skill should be used. Over-broad invocation increases the chance of unintended external tool use, credential prompting, package installation, or content-generation workflows being launched without sufficient user intent validation.
The skill instructs use of npx @iqinghu/qhkit without pinning an exact version, so execution can pull whatever package version is current at runtime. That creates a supply-chain risk: a compromised upstream release or unexpected breaking change could execute arbitrary code on the host when the skill is triggered.
This duplicated finding points to the same persistence behavior: unpacking software into a user directory and exporting a modified PATH, potentially across sessions via shell profile changes. Even with hash verification, persistent path changes expand long-term attack surface and can alter which binaries future commands resolve to.
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: unpacking software into a user directory and exporting a modified PATH, potentially across sessions via shell profile changes. Even with hash verification, persistent path changes expand long-term attack surface and can alter which binaries future commands resolve to.
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 fallback command npx --yes sharp-cli fetches and executes the latest package version dynamically, which is a classic unpinned package execution pattern. If the npm package or one of its dependencies is compromised, the host may run attacker-controlled code during image processing.
The document states '默认语言 简体中文', which is a natural-language locale constraint. Because the skill does not present this as a user-selectable preference or obtain opt-in at this point, it can violate language/locale policy expectations for user choice.