redbook

This code is not overtly malware (no execution of commands, no network calls, no filesystem access), but it is designed to generate opaque, authentication/anti-bot style signatures and fingerprints. It hardcodes a secret key (B1_SECRET_KEY) and uses RC4/XOR/custom base64 encoding to hide how request headers are constructed. It also serializes all cookies and embeds them into the fingerprint material that becomes part of returned headers (x-s-common), creating potential privacy/exfiltration risk depending on how the calling application uses these headers.

该技能的功能与“小红书内容分析”基本一致，但其实现依赖个人发布的外部 CLI，并要求使用本地浏览器登录 cookie 进行认证，带来中等偏高的供应链与凭证暴露风险。未见明确恶意、隐藏外传或非官方中转端点，因此更适合判定为可疑/高敏感集成而非恶意技能。

The code provides a high-sensitivity capability to harvest authentication/session cookies for xiaohongshu.com from a local Chrome profile using CDP (Network.getAllCookies), including reuse of an existing localhost CDP session and a fallback that copies cookie databases into a temporary directory to overcome profile locking. No obfuscation is present, and localhost-only CDP communication is shown; however, returning cookie values directly to the caller is effectively credential theft functionality and should be treated as a significant security/abuse risk in supply-chain contexts.

This code is a credential-access component: it programmatically collects and returns sensitive authentication/session cookies for xiaohongshu.com from local browser profiles (including automatic Chrome profile enumeration) and includes a CDP-based fallback explicitly intended to bypass encryption/protection barriers. While this fragment does not itself show network exfiltration, its core functionality provides high-impact session token material to downstream logic, making it a substantial supply-chain security risk if misused or integrated into unauthorized workflows.

No clear signs of overt malware (no backdoor, credential theft, or explicit exfiltration behavior) are present in the provided fragment. However, it creates a meaningful attack surface by injecting Markdown-derived HTML into a real headless Chromium page via page.setContent without visible sanitization while launching Chromium with '--no-sandbox'/'--disable-setuid-sandbox'. It also permits execution of an arbitrary local binary via CHROME_PATH and performs filesystem writes under a caller-controlled outputDir. If Markdown/options/CHROME_PATH are not fully trusted, this module should be treated as security-sensitive and hardened (e.g., sanitize/escape HTML, avoid disabling sandbox, and restrict outputDir/binary selection).