Which versions of chromecast-receiver are malicious?

The following npm versions of chromecast-receiver are flagged malicious: 2.0.9, 2.0.10. Treat any of these as compromised.

How do I remediate chromecast-receiver if I installed it?

Remove chromecast-receiver from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If chromecast-receiver was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is chromecast-receiver part of a known attack campaign?

Yes — chromecast-receiver is associated with the RLMA-2026-01205 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-receiver across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chromecast-receiver (2 malicious versions).

Malicious package

chromecast-receivernpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

chromecast-receiver is a confirmed malicious npm package (MAL-2026-1691) that executes malicious code on install (malicious versions 2.0.9, 2.0.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chromecast-receiver (npm)

MAL-2026-1691

Immediate action

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

npm uninstall chromecast-receiver

What this malware does

The package chromecast-receiver was found to contain malicious code.

Malicious versions

2 flagged

2.0.92.0.10

Indicators of compromise (SHA-256)

66373fa3570129f6f515b2bf7fdbfa5670ef2ab18bca7e8e9d5f6e4c57ca44b2

9ded3cbd70f99d1eeed4d998a82b13da94a22539d5783a36ad7c2651a01ca724

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chromecast-receiver (2 malicious versions).
If you installed it — respond
Remove chromecast-receiver from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If chromecast-receiver was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. chromecast-receiver on npm has been identified as a malicious package (versions 2.0.9, 2.0.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01205

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks chromecast-receiver-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database