T03 · Remote Payload Retrieval and Execution
- Location
references/quick-start.md:10- Finding
Mutable Remote Installer Is Executed Directly Through Bash
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for real Xiaohongshu account automation, but its recommended installer and some account-action safeguards need careful review before use.
Install only after reviewing the installer or using manual, pinned steps; avoid piping remote scripts to bash. Treat the cookie file like a login credential, keep it in a private location, and require an explicit preview and confirmation before any publish, comment, like, or favorite action on your account.
references/quick-start.md:10Mutable Remote Installer Is Executed Directly Through Bash
references/quick-start.md:17Unpinned Third-Party Packages and Browser Components Create Supply-Chain Exposure
The | bash construct turns downloaded network content directly into shell input, eliminating any review barrier and making compromise of the source immediately lead to arbitrary command execution. In installation docs this is a classic high-risk chaining pattern and is more dangerous because it is marked as the recommended path.
curl -fsSL https://raw.githubusercontent.com/sipingme/xiaohongshu-mcp-node-skill/main/install.sh | bash
The skill advertises automated posting and engagement actions without clearly requiring explicit user confirmation before irreversible social-media operations. In an agent setting, this increases the chance of accidental publication, unwanted interactions, or abuse of the user's authenticated account.
The installation step invokes Playwright via an unpinned command, which weakens supply-chain reproducibility and can cause users to fetch an unexpected upstream version. In a skill that drives browser automation, dependency drift can introduce vulnerable code or behavioral changes without the operator noticing.
The login flow describes QR authentication and automatic cookie saving but does not prominently warn users about local storage, persistence, and sensitivity of authentication cookies. If users mishandle the cookie file, an attacker could reuse it to access the associated Xiaohongshu account.
The security section claims communications are limited to Xiaohongshu, but the document also states image inputs may come from arbitrary URLs and be auto-downloaded. That mismatch can mislead users about outbound network behavior and create SSRF-like or privacy risks if the tool fetches attacker-controlled URLs from trusted environments.
This markdown file is natural-language documentation, and all user-facing instructions are presented only in Chinese. Under the policy rule for language/locale, forcing a single language without user opt-in or a documented regional justification is a violation.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
**安全措施**:
- Cookie 仅存储在本地
- 不会上传到任何服务器
- 建议设置文件权限:`chmod 600 cookies.json`
### Q19: 会不会被小红书封号?
The guide recommends curl ... | bash, which downloads and immediately executes remote code from the repository's default branch without review or integrity verification. If the repository, branch, or delivery path is compromised, users will run attacker-controlled shell commands on their machine.
The quick-start uses npx playwright install chromium without pinning a specific package version, so the resolved package may vary over time. In setup documentation this creates a supply-chain risk and weakens reproducibility, especially because users are encouraged to run it during installation of a skill that also automates account actions.
The publishing example shows a live xhs-cli publish workflow but does not clearly warn that it will post content to the user's actual Xiaohongshu account. In a skill for social-platform automation, omission of that warning increases the chance of unintended public posting, account misuse, or reputational harm.
The manifest description and the full skill documentation appear to require Chinese for use, but there is no statement that the skill is Chinese-only by design or that users may choose another language. This can violate language/locale policy when a skill forces a specific language without opt-in or justification.
The privacy text says all operations execute locally, but the documented core actions necessarily perform remote operations against Xiaohongshu. This is a deceptive or inaccurate assurance that can cause users to underestimate account, privacy, and audit implications of using the skill.
The skill documentation forces a single language presentation throughout the file and does not indicate that the skill is intentionally limited to Chinese-speaking users or provide an alternate language option. Under the stated policy, imposing a language without opt-in can be a natural-language policy issue.
The document instructs users to fetch a script from GitHub raw content and execute it locally. External script fetching is especially dangerous here because it is paired with immediate execution and targets end-user environments during installation.
curl -fsSL https://raw.githubusercontent.com/sipingme/xiaohongshu-mcp-node-skill/main/install.sh | bash
The command table lists like and comment operations without any notice that they trigger real engagement actions on the logged-in account. Because this skill controls a live social-media account, users may invoke these actions unintentionally and create unauthorized or unwanted interactions.