chrome-automation

SUSPICIOUS: the skill's browser-control purpose is coherent, and most dependencies are legitimate, but it mandates running opaque local installer scripts and a curl|sh Rust bootstrap before use. It also copies existing Chrome login state into an automation profile and grants a powerful external browser CLI control over authenticated sessions, making the overall footprint high-risk though not confirmed malicious.

No overt malicious payload (e.g., credential theft, explicit exfiltration, reverse shells) is present in this shell wrapper itself; however, it is a high-risk supply-chain execution orchestrator. It clones an unpinned upstream repository, runs pnpm install and a native build (which commonly execute arbitrary lifecycle/build scripts from the fetched code and dependency tree), installs Chromium via npx downloads, and—most critically—executes a network-delivered installer script via curl | sh for rustup without additional verification. If upstream code or any downloaded dependencies are compromised, this script provides an end-to-end path from untrusted network content to executable artifacts on the host.

No clear supply-chain malware behavior is present (no obfuscation, no explicit exfiltration, no backdoor execution). The primary security concern is legitimate-but-risky operational behavior: it clones authenticated Chrome session state into a persistent automation profile and starts Chrome with remote debugging enabled on a fixed port (9222). If that debug interface is reachable by untrusted parties or if the automation profile directory is exposed, the script can enable session hijacking or browser control. Review and harden usage (e.g., restrict network access to localhost, reduce persistence of sensitive session data, and ensure strict filesystem permissions).

No direct indicators of stealthy malware behavior (e.g., credential theft, exfiltration, persistence, or reverse shells) are evident in this fragment. However, the script significantly increases supply-chain execution risk by (1) cloning an unpinned remote repository, (2) running pnpm install and npm run build:native which can execute lifecycle/build scripts from untrusted remote content, and (3) downloading and executing rustup-init.exe without visible checksum/signature verification. This is likely a legitimate installer, but it should be treated as a high-trust bootstrapper and reviewed/hardened (pin repo revision, enforce lockfiles, verify downloads, consider restricting lifecycle scripts).

No direct indicators of embedded malware (no downloads, no credential-stealing/exfiltration code, no obfuscated payloads, no persistence beyond normal profile storage). However, the script materially increases privacy/account takeover risk by (1) copying/importing existing Chrome profile state (including likely authentication/session-relevant data) into a persistent automation directory and (2) enabling Chrome DevTools remote debugging on a fixed port (9222), creating a potentially dangerous control surface if reachable beyond the intended trust boundary. Treat as a high-impact automation/session-security risk requiring strict access controls to both the debug port and the profile directory.