T08 · Insecure Dependencies
- Location
references/mcp-config.md:5- Finding
Unverified Third-Party Authentication Executables
- Content
View full analysis
Vulnerability Details
File Location:
references/mcp-config.md:5-25
Vulnerability Type: Unverified third-party executable dependency
Risk Level: MediumVulnerable Code Snippet
text https://github.com/xpzouying/xiaohongshu-mcpbash ./xiaohongshu-mcp-{platform} [-headless] [-port :18060] ./xiaohongshu-login-{platform}Technical Analysis
The installation documentation directs users to obtain and execute an MCP service and login utility from a mutable personal GitHub repository. It does not pin an immutable release or commit, provide cryptographic checksums or signatures, identify verified release artifacts, or require a reviewed and reproducible source build.
These executables have access to the user's Xiaohongshu authentication workflow and stored session cookies. Consequently, compromise of the upstream repository, its release artifacts, or the download channel could introduce modified executable code after this Skill has already been reviewed. The issue is therefore an insecure software supply-chain dependency rather than confirmed malicious behavior within the repository itself.
The same unpinned upstream repository is also referenced in
SKILL.md:68.Attack Path
- An attacker compromises the referenced repository, its maintainer account, or a release artifact.
- The attacker replaces the expected MCP server or login executable with a modified binary.
- A user follows the Skill documentation and downloads the executable without checksum or signature verification.
- The user runs the modified login utility or MCP service with their normal operating-system privileges.
- The executable captures Xiaohongshu session data, performs unauthorized account actions, reads files accessible to the user, or executes other code under the user's account.
Impact Assessment
Successful exploitation could provide the malicious dependency with the same local privileges as th ...[truncated 458 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a specific reviewed release and immutable commit hash.
- Provide exact release artifact URLs rather than directing users to a mutable repository landing page.
- Publish SHA-256 or stronger checksums for every supported platform and require verification before execution.
- Prefer cryptographically signed release artifacts and document signature verification using a pinned maintainer key.
- Where practical, require building from the pinned source revision through a documented and reproducible build process.
- Run the MCP server and login utility with least privilege in an isolated account or sandbox with restricted filesystem and network access.
- Document where cookies are stored, apply restrictive file permissions, and ensure session data is not exposed to unrelated local processes.
- Establish a dependency-update review process so that version changes trigger renewed source and artifact verification.
