Security audit
Security checks for vulnerabilities and agentic risk
The skill’s Amazon keyword lookup purpose is clear, but it also tells the agent to install and update runtime tools, alter PATH, and store API credentials, which should be reviewed before use.
Install only if you are comfortable allowing this skill to install or update qhkit/Node tooling and configure a Qinghu API token. Prefer preinstalling a reviewed, pinned qhkit version yourself, avoid npx/@latest runtime execution, and approve paid qhkit calls only after checking the estimated credits.
The description says the skill must trigger when the user says three example phrases "or raises similar needs" ("或提出同类需求时必须触发"). That catch-all language does not define clear boundaries for what counts as similar, increasing the risk of unintended invocation on adjacent Amazon optimization questions.
The skill goes far beyond ASIN keyword lookup by directing the agent to install Node/qhkit, modify PATH, configure credentials, and bootstrap the environment. That expands the attack surface from a data query skill into host modification and secret-handling behavior, increasing the chance of unsafe changes, credential exposure, or unintended execution in the user's environment.
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, that creates a software supply-chain risk because behavior can change unexpectedly or a compromised upstream package could run code on the host during installation/execution.
This duplicate finding points to the same persistence behavior: writing Node binaries into the user's home directory and changing PATH. In the context of a skill that should only perform ASIN keyword reverse lookup, persistent environment changes are unnecessary and materially increase system and supply-chain risk.
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: writing Node binaries into the user's home directory and changing PATH. In the context of a skill that should only perform ASIN keyword reverse lookup, persistent environment changes are unnecessary and materially increase system and supply-chain risk.
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 only three short example utterances without clarifying scope, required constraints, or non-matching cases. Because there are no exclusions or negative examples, neighboring requests about Amazon ads or keyword analysis could be interpreted as triggers inconsistently.