agent-browser
Audited by Socket on Jul 23, 2026
2 alerts found:
Securityx2SUSPICIOUS. The stated purpose matches browser automation, but the footprint is high-risk: it installs another skill transitively, routes activity through a remote service, and grants an agent arbitrary web interaction including uploads and form submission. The main concern is broad autonomous browsing/action capability plus indirect prompt-injection exposure, not confirmed malware.
The provided fragment contains a clear high-sensitivity capability: it automates login and then harvests authenticated browser cookies via injected JavaScript (document.cookie), parses the results, and echoes the cookies to stdout. Even without visible malware behaviors beyond browser automation, this is strongly aligned with session/credential harvesting patterns and should be treated as a significant supply-chain/security risk unless strictly confined to an isolated, controlled test environment with strict access controls and output redaction. Additional context (full login implementation, whether cookies are actually emitted, and how outputs are handled in the consuming project) would be needed to reduce uncertainty about malicious intent.