T08 · Insecure Dependencies
Warning
- Location
SKILL.md:12- Finding
Unaudited Third-Party CLI Installed Globally and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 12-26
Vulnerability Type:T08: Insecure Dependencies
Risk Level: Mediumbash ## Prerequisites ```bash npm install -g awal@2.0.3 awal auth loginUsage
bash npx awal@2.0.3 x402 pay \ https://anicca-proxy-production.up.railway.app/api/x402/intent-router \ -X POST \ -d '{"text":"I want to book a flight to Tokyo next week","intents":["booking","complaint","question","feedback","cancellation"],"language":"en"}'text ### Technical Analysis The skill instructs users to install the third-party `awal` npm package globally and then execute it for authentication, payment, and remote API access. The package is pinned to version `2.0.3`, which reduces uncontrolled version drift, but the project does not include its implementation, an integrity hash, a lockfile, provenance information, or evidence that the package and its transitive dependencies were independently reviewed. A global npm installation can execute package lifecycle scripts and places executable files in the user's global npm environment. The subsequent `awal auth login` and `npx awal@2.0.3 x402 pay` commands execute code supplied through the npm distribution channel. If the named package version, publisher account, registry response, or a transitive dependency is compromised, attacker-controlled code could run with the invoking user's privileges. The CLI is also used for authentication and cryptocurrency payment operations. A compromised implementation could potentially access authentication artifacts, alter payment destinations or parameters, inspect local files available to the user, or transmit additional information beyond the documented classification request. ### Attack Path 1. An attacker compromises the npm publisher account, the referenced package release, or a dependency resolved during installation. 2. The user follows the documented prerequisite and runs `npm install -g awal@2.0.3`. 3. Malicious lif ...[truncated 1363 chars]- Remediation
View remediation
Remediation Suggestions
- Avoid global installation. Run the dependency in an isolated, least-privileged environment or add it as a project-local development dependency.
- Publish and verify package provenance, including the expected npm publisher, source repository, release process, and cryptographic integrity digest.
- Use a lockfile or equivalent integrity-controlled dependency manifest that covers the package and its complete transitive dependency tree.
- Audit the exact
awal@2.0.3package contents, lifecycle scripts, transitive dependencies, authentication storage, and payment handling before recommending execution. - Disable npm lifecycle scripts during installation where compatible, then explicitly invoke only reviewed setup steps.
- Do not perform installation or execution as root or an administrator. Use a container, sandbox, or restricted operating-system account with minimal filesystem and network access.
- Document where authentication tokens are stored, their permissions, expiration behavior, and how users can revoke them.
- Require explicit confirmation of payment amount, destination, network, and request contents before submitting a transaction.
- Warn users that the request sends supplied text and optional context to
anicca-proxy-production.up.railway.app; advise against submitting secrets or regulated personal data unless the service's privacy and retention controls have been reviewed.