browse

This documentation is not itself malware, but it prescribes an operational workflow that routes all browser automation through a remote Browserbase session with powerful evasion and recording features. That architecture centralizes and persists sensitive data (credentials, cookies, full HTTP request/response bodies, session videos) in an external service controlled by whoever holds BROWSERBASE_CONNECT_URL and BROWSERBASE_DEBUG_URL. Absent clear provenance, access controls, and retention policies, this pattern materially increases the risk of credential harvesting, privacy breaches, and abusive scraping. Treat the service as untrusted by default: do not use real secrets, verify operator identity and endpoint security, and minimize enabling network/session capture.