Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to perform the advertised Amazon category lookup, but it also tells agents to install or upgrade command-line software and Node in the user's environment automatically.
Review this carefully before installing. It is not showing evidence of theft or sabotage, but it may download and install Node/qhkit, alter PATH for the session or shell, upgrade packages, and store a qhkit token. Prefer a controlled environment with preinstalled, pinned qhkit and provide API credentials only when you understand the credit charges.
The instruction says to translate the keyword into the target site's or country's language before calling the tool. This imposes a language/locale transformation by default rather than offering the user a choice, which can conflict with language/locale policy expectations.
This skill is supposed to query Amazon category nodes, but it also instructs the agent to install Node, install packages globally, configure tokens, and modify the runtime environment. Expanding from data lookup into software installation materially enlarges the attack surface and could cause unreviewed code execution on the host.
The skill recommends running npx @iqinghu/qhkit without pinning an exact version. That causes execution of whatever package version is current at invocation time, increasing supply-chain risk and making behavior non-reproducible if a compromised or breaking release is published.
The duplicated finding reflects the same persistence issue: the documented setup stores Node in the user's home directory and modifies execution paths as part of fulfilling a simple lookup skill. That is risky because a narrowly scoped skill should not normalize persistent host modification to satisfy routine requests.
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 duplicated finding reflects the same persistence issue: the documented setup stores Node in the user's home directory and modifies execution paths as part of fulfilling a simple lookup skill. That is risky because a narrowly scoped skill should not normalize persistent host modification to satisfy routine requests.
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"
No suspicious patterns detected.