Which versions of chromecast-webdriver-cli are malicious?

The following npm versions of chromecast-webdriver-cli are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate chromecast-webdriver-cli if I installed it?

chromecast-webdriver-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed chromecast-webdriver-cli — how do I know if it already compromised me?

If chromecast-webdriver-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is chromecast-webdriver-cli part of a known attack campaign?

Yes — chromecast-webdriver-cli is associated with the IN-MAL-2026-018331 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find chromecast-webdriver-cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chromecast-webdriver-cli (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chromecast-webdriver-cli across your stack and pipelines.

Malicious package

chromecast-webdriver-clinpm

chromecast-webdriver-cli is a confirmed malicious npm package (MAL-2026-14231) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chromecast-webdriver-cli (npm)

MAL-2026-14231

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall chromecast-webdriver-cli

What this malware does

[email protected] runs a postinstall lifecycle script that collects host metadata (os.hostname(), platform, arch, node version, package name, npm lifecycle event) and POSTs it as JSON to the hardcoded host h77svwt7.instances.poc.jchunt.top at /chromecast-webdriver-cli on every npm install. The destination is an anonymous subdomain unrelated to the upstream project the package name references (shaka-project/generic-webdriver-server). No opt-in, no first-party publisher relationship, and no functional package code — the beacon fires automatically and transmits installer-identifying data to a third-party endpoint. The package name reproduces a legitimate-sounding upstream tool, which is the fingerprint of a dependency-confusion / typosquat beacon.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0c858cd5357d77c39366f7bd1cc1985a5d7012d33da45d6dc9667544b54198d6

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chromecast-webdriver-cli (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chromecast-webdriver-cli across your stack and pipelines.
If you installed it — respond
chromecast-webdriver-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If chromecast-webdriver-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks chromecast-webdriver-cli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. chromecast-webdriver-cli on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018331

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chromecast-webdriver-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database