T08 · Insecure Dependencies
- Location
README.md:168- Finding
Mutable npm Package Execution Through npx
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This NVIDIA CUDA skill is coherent and purpose-aligned, with optional local GPU probes and benchmarks but no hidden persistence, exfiltration, or destructive behavior found.
Install only if you want an agent to inspect CUDA/PyTorch runtime details and run local GPU benchmarks or code scans. Treat probe output as potentially sensitive system information, install PyTorch in an isolated environment, and prefer pinned CLI/package versions if you follow the optional publication or requirements commands.
README.md:168Mutable npm Package Execution Through npx
requirements.txt:1Unbounded PyTorch Dependency Version
Code enumerates, copies, or searches environment variables for secrets. Bulk environment access can collect credentials unrelated to the skill's stated purpose.
recommendations.append("CUDA is unavailable. Verify driver, runtime, and container visibility first.")
return recommendations
if any(token in names for token in ("H100", "H200", "B200", "BLACKWELL", "HOPPER")):
recommendations.append("Prefer BF16 as the baseline precision on Hopper/Blackwell-class GPUs.")
if any(token in names for token in ("H200", "B200", "BLACKWELL")):
recommendations.append("Benchmark newer flash attention implementations and cuDNN/TE attention, not only the default SDPA path.")
Code enumerates, copies, or searches environment variables for secrets. Bulk environment access can collect credentials unrelated to the skill's stated purpose.
recommendations.append("CUDA is unavailable. Verify driver, runtime, and container visibility first.")
return recommendations
if any(token in names for token in ("H100", "H200", "B200", "BLACKWELL", "HOPPER")):
recommendations.append("Prefer BF16 as the baseline precision on Hopper/Blackwell-class GPUs.")
if any(token in names for token in ("H200", "B200", "BLACKWELL")):
recommendations.append("Benchmark newer flash attention implementations and cuDNN/TE attention, not only the default SDPA path.")
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# nvidia-cuda
`nvidia-cuda` is an open-source skill package for Codex, OpenClaw, and similar agent systems that need to write or review deep learning code for NVIDIA GPUs.
It is opinionated on purpose. The package encodes modern AI infra practice for H100, H200, and B200-class systems:
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
### Codex
Copy this directory to your skills path as `~/.codex/skills/nvidia-cuda/`.
### OpenClaw / ClawHub-compatible agents
The README recommends running npx clawhub@latest publish ., which fetches and executes the latest package version at publish time without pinning or prior verification. This creates a supply-chain risk: a compromised or malicious newly published version could execute arbitrary code on the publisher's machine or CI environment.
The skill instructs the agent to inspect local runtime state and files, including environment variables, hardware details, and local reference documents, but it does not declare any explicit tool scope such as permissions or allowed-tools. That creates an authorization gap: a caller may invoke a skill that implicitly relies on env and file-read capabilities without clear boundary-setting, increasing the chance of unintended disclosure of sensitive environment data or local file contents.
The dependency is specified as torch>=2.11 without an upper bound or exact pin, which makes builds non-reproducible and can silently pull in different releases over time. In a GPU/AI infrastructure skill centered on PyTorch, this increases supply-chain and stability risk because a vulnerable or breaking torch release could be installed without review.
torch>=2.11
requirements.txt references torch without pinning a specific version, while PyTorch has multiple published advisories affecting some releases. Because the manifest allows any version at or above 2.11, it is impossible to verify from this file alone whether installation will resolve to a safe version, and the skill's heavy reliance on PyTorch makes that uncertainty more significant.