Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent LinkPix/qhkit video-generation skill, with disclosed setup, API-token, upload, and cost-related behaviors that users should understand before use.
Before installing, be comfortable with the skill installing or invoking qhkit from npm, configuring a qhkit token, uploading the media files you provide to the service, and spending service credits for generation. Prefer reviewing the qhkit package and approving environment changes before first use.
The description says the skill 'must trigger' whenever a user asks for ad blockbusters, brand promos, cinematic product videos, or premium-feel TVCs, and then lists many broad keywords. These phrases are common in ordinary creative requests and the file does not provide exclusion conditions or narrower scope boundaries, increasing the chance of unintended invocation.
The skill recommends running npx @iqinghu/qhkit without pinning a specific version, which causes code to be fetched and executed at runtime from the package registry. That creates a supply-chain risk: a compromised or newly published package version could execute unexpected code in the user's environment, especially because the surrounding guidance encourages automatic environment bootstrapping.
This duplicate finding points to the same persistence behavior: installing binaries into the user's home directory and exporting a modified PATH can influence future command resolution beyond the immediate task. In a skill that also encourages fetching packages and running CLI tools, this makes the environment more sensitive to later misuse or confusion about which binary is being executed.
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 into the user's home directory and exporting a modified PATH can influence future command resolution beyond the immediate task. In a skill that also encourages fetching packages and running CLI tools, this makes the environment more sensitive to later misuse or confusion about which binary is being executed.
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 instructions require directing users to the domestic iqinghu.com site and explicitly say not to guide users toward the international site unless they clearly state they use it. This imposes a locale-specific workflow by default rather than offering a user choice or opt-in, which is a natural-language locale policy concern.
The trigger section lists two example utterances, but it does not define the full trigger set or include non-trigger examples. Without negative examples or constraints, the activation criteria remain underspecified and may overlap with routine requests for promotional content.
No suspicious patterns detected.