T08 · Insecure Dependencies
- Location
SKILL.md:22- Finding
Unverified Downloaded Installer Executes with Root Privileges
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is mostly a normal IPFS server operations skill, but it includes root-level installer guidance and credential-handling examples that deserve review before use.
Review the installation path before using it. Prefer a trusted package manager or verify Kubo checksums/signatures before running any downloaded installer with sudo. Keep the IPFS API bound to localhost unless you have firewalling and authentication in place, be deliberate before exposing a public gateway, and avoid entering real remote-pinning JWTs directly into shell history or shared terminals.
SKILL.md:22Unverified Downloaded Installer Executes with Root Privileges
SKILL.md:99Remote Pinning JWT Is Exposed Through Command-Line Arguments
The README encourages users to initialize and run an IPFS node and highlights gateway services, peer management, and API-related capabilities without warning that these actions may expose network services, consume significant bandwidth/storage, or unintentionally make content accessible to others. In the context of an infrastructure skill, omission of these operational security warnings can lead users to deploy a reachable node or gateway with insufficient access controls and poor understanding of the resource and privacy implications.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
curl -O https://dist.ipfs.tech/kubo/v0.24.0/kubo_v0.24.0_darwin-amd64.tar.gz tar -xzf kubo_v0.24.0_darwin-amd64.tar.gz sudo ./kubo/install.sh
## Node Initialization
The skill includes a remote pinning command that takes a JWT credential inline but does not warn users against pasting real secrets into shell history, logs, screenshots, or shared terminals. In an agent skill focused on operational commands, this increases the chance of credential exposure and unauthorized use of the remote pinning account.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Remote pinning services:
# Configure remote pinning (Pinata, Web3.Storage, etc.)
ipfs pin remote service add pinata https://api.pinata.cloud/psa YOUR_JWT
# Pin to remote service
ipfs pin remote add --service=pinata --name="my-content" QmHash
No suspicious patterns detected.