cookie-sync

The supplied text is documentation for a legitimate-looking but high-risk browser cookie synchronization workflow. It transfers active authentication cookies to a third-party cloud browser and uses them to access sensitive services. No direct malware or obfuscation is present in the shown material, but use should require explicit authorization, trusted service configuration, strict context isolation, short-lived sessions, and careful protection of API keys, cookies, and screenshots.

The code is readable and appears purpose-built to synchronize local browser authentication cookies into Browserbase. It is not evidently malware, but it performs a high-impact credential transfer: browser session cookies are uploaded to a persistent third-party cloud context. Users should restrict --domains, verify the CDP endpoint is local and trusted, protect BROWSERBASE_API_KEY and the Browserbase context, and avoid using the tool with sensitive profiles unless this transfer is intended.

No executable code was provided, so malicious behavior cannot be directly established. The documented design intentionally exports all local browser cookies and persists them in Browserbase, creating a significant credential exposure risk if the account, context, API key, or CDP endpoint is compromised or misconfigured. The behavior appears aligned with the stated purpose rather than covert malware, but implementation and deployment security require review.