T08 · Insecure Dependencies
- Location
SKILL.md:72- Finding
Unpinned Third-Party Installation Can Execute Mutable Supply-Chain Code
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:72-81;references/quick-start.md:15-16;references/faq.md:9-10;references/troubleshooting.md:18-25
Vulnerability Type: Unpinned and potentially privileged third-party dependency installation
Risk Level: HighVulnerable Code
SKILL.md:72-81:bash npm install -g toutiao-mcp # Install browser npx playwright install chromium # Alternative: build from source git clone https://github.com/sipingme/toutiao-mcp.git cd toutiao-mcp npm install npx playwright install chromium npm run buildreferences/quick-start.md:15-16andreferences/faq.md:9-10:bash npm install -g toutiao-mcp npx playwright install chromiumreferences/troubleshooting.md:18-25:bash # Use sudo (not recommended) sudo npm install -g toutiao-mcp # Or configure an npm global directory (recommended) mkdir ~/.npm-global npm config set prefix '~/.npm-global' echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc source ~/.bashrc npm install -g toutiao-mcpTechnical Analysis
The installation instructions retrieve and execute mutable third-party content without pinning an exact npm package version, Playwright version, Git commit, or integrity digest. The source-build path clones the repository's current default branch and runs
npm installandnpm run build. These operations may execute package lifecycle scripts and other code that was not included in this audited artifact.The
npx playwrightinvocation is also not version-pinned. Depending on the local environment and npm behavior,npxmay resolve or download a package dynamically. Consequently, the effective installation payload can change after this skill documentation has been reviewed.The troubleshooting guide compounds the risk by suggesting
sudo npm install -g toutiao-mcp. Although marked as not recommended, following this command permits package lifecycle ...[truncated 2200 chars]- Remediation
View remediation
Remediation Suggestions
- Pin
toutiao-mcpto an explicitly reviewed version rather than installing the mutable latest release:bash npm install -g toutiao-mcp@<reviewed-exact-version> - Pin Playwright to a reviewed exact version and avoid an unconstrained
npxresolution:bash npx playwright@<reviewed-exact-version> install chromium - For source installations, check out a reviewed immutable commit rather than relying on the repository's default branch:
bash git clone https://github.com/sipingme/toutiao-mcp.git cd toutiao-mcp git checkout <reviewed-commit-hash> - Publish and verify expected package integrity hashes or signatures. Document the trusted package owner, version, commit, and checksum together.
- Include and review a lockfile, then use
npm cito obtain deterministic transitive dependencies. - Audit all npm lifecycle and build scripts before execution. Use
--ignore-scriptswhere the package can function without lifecycle scripts, and explicitly document any scripts that must be enabled. - Remove the
sudo npm installrecommendation entirely. Use an unprivileged user-owned npm prefix, a dedicated service account, or an isolated container instead. - Run the MCP server with least privilege. Restrict filesystem access to dedicated cookie, data, and approved media directories, and restrict outbound network access to required Toutiao endpoints.
- Protect the cookie file with owner-only permissions, avoid exposing it in debug logs or issue reports, and rotate the Toutiao session if package compromise is suspected.
- Vendor or include the reviewed MCP implementation in the audit scope so its privacy, download validation, browser automation, and credential-handling claims can be verified.
- Pin