Which versions of player-common-controls are malicious?

The following npm versions of player-common-controls are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate player-common-controls if I installed it?

Remove player-common-controls 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 player-common-controls — how do I know if it already compromised me?

If player-common-controls 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 player-common-controls part of a known attack campaign?

Yes — player-common-controls is associated with the RLMA-2026-01497 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 player-common-controls across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for player-common-controls (version 100.0.0).

Malicious package

player-common-controlsnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

player-common-controls is a confirmed malicious npm package (MAL-2026-1820) that executes malicious code on install (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in player-common-controls (npm)

MAL-2026-1820

Immediate action

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

npm uninstall player-common-controls

What this malware does

The package player-common-controls was found to contain malicious code.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

45994b110ffba816ecdef90d0ea56d3cdb6c133a8dfc67b3c3c3c08251d67e43

1aef58425992286c8ee1bba6bb26ba161a52a852bb7ed8a6087e737b91d02e8b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for player-common-controls (version 100.0.0).
If you installed it — respond
Remove player-common-controls 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 player-common-controls 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. player-common-controls on npm has been identified as a malicious package (version 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01497

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks player-common-controls-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