T08 · Insecure Dependencies
- Location
SKILL.md:20- Finding
Unpinned External npm Package Is Automatically Retrieved and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 20–25, 73–76, and 97–101
Vulnerability Type: Unreviewed and unpinned third-party dependency execution
Risk Level: HighVulnerable Code
yaml install: - kind: node package: yyds-auto-mcp bins: [yyds-auto-mcp]bash npm install -g yyds-auto-mcpjson { "mcpServers": { "yyds-auto": { "command": "npx", "args": ["-y", "yyds-auto-mcp"], "env": { "YYDS_DEVICE_HOST": "127.0.0.1", "YYDS_DEVICE_PORT": "61140" } } } }Technical Analysis
The Skill instructs users and compatible runtimes to retrieve and execute
yyds-auto-mcpfrom npm without pinning an exact version or integrity digest. Thenpx -yconfiguration also permits package retrieval and execution without an interactive confirmation step.The audited project contains only
SKILL.md; the npm package implementation is not included. Its executable behavior therefore cannot be verified against the documentation during this audit, and its effective payload may change after the Skill has been reviewed. This creates a supply-chain trust boundary in which package compromise, account takeover, or an unexpectedly unsafe future release could introduce arbitrary host-side code.The package is intended to access a powerful Android automation interface. Documented capabilities include elevated shell execution at line 167, arbitrary Python execution at line 187, file operations, APK installation, and delegated AI-agent execution at line 195. These capabilities amplify the consequences of dependency compromise.
No evidence establishes that the current npm package is malicious. The confirmed issue is the unsafe, mutable, and unreviewed dependency execution mechanism.
Attack Path
- A user installs the Skill or configures the documented MCP server.
- The installation mechanism runs
npm install -g yyds-auto-mcp, or MCP startup invokesnpx -y yyds-auto-mcp...[truncated 1295 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
yyds-auto-mcpto a specific, reviewed version rather than resolving an unconstrained release. - Record and verify package integrity with a lockfile and cryptographic integrity hash.
- Remove
npx -yfrom the recommended configuration. Require explicit installation and approval before first execution. - Vendor the executable implementation into the reviewed distribution, or otherwise make its exact source available for security review.
- Use a trusted private registry or tightly controlled package mirror where appropriate.
- Verify package provenance and signatures during installation, and monitor the publisher account and releases for compromise.
- Run the MCP server in a sandbox or dedicated low-privilege account with restricted filesystem, environment-variable, process, and network access.
- Disable elevated shell, Python execution, package management, APK installation, and unrestricted file operations unless they are explicitly required.
- Apply an allowlist to device operations and require confirmation for destructive or privilege-sensitive actions.
- Authenticate and encrypt communications with remote Android devices, particularly when connections extend beyond ADB forwarding or localhost.
- Pin the reviewed package version in all installation metadata and example configurations so automated installation cannot silently select a different payload.
- Pin
