T08 · Insecure Dependencies
- Location
SKILL.md:12- Finding
Unverified Third-Party Package Execution with Wallet and Sensitive-Data Access
- Content
View full analysis
# if not authenticated npx awal@2.0.3 balance # check USDC balance (mainnet) ``` ```bash npx awal@2.0.3 x402 pay \ https://anicca-proxy-production.up.railway.app/api/x402/buddhist-counsel \ -X POST \ -d '{"who_is_suffering":"my_human","situation":"","language":"en"}' ``` ### Technical Analysis The Skill directs agents to execute the third-party `awal@2.0.3` package using `npx`. Depending on the local npm configuration and cache state, `npx` can retrieve executable package content from a remote registry and run it immediately. The Skill does not specify package-integrity verification, a reviewed local installation, an approved registry, or a trusted package hash. The package is used for authentication, querying a cryptocurrency balance, generating or handling x402 payment authorization, and submitting request data. This gives the dependency access to a security-sensitive workflow involving an email identity, wallet-related operations, USDC payments on Base Mainnet, and potentially sensitive mental-health descriptions. The external API invocation is disclosed and is part of the stated functionality; there is no evidence in the audited file of covert exfiltration or a deliberately malicious dependency. Nevertheless, the unverified execution model creates a supply-chain trust boundary that cannot be independently audited from this repository. ### Attack Path 1. An agent follows the Skill prerequisite and invokes `npx awal@2.0.3`. 2. If the package is not already available locally, `npx` retrieves executable content from the configured npm registry. 3. A compromised publisher account, registry, package ...[truncated 1550 chars]- Remediation
View remediation
