Which versions of player-button are malicious?

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

How do I remediate player-button if I installed it?

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

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

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

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

Malicious package

player-buttonnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

player-button is a confirmed malicious npm package (MAL-2026-1818) 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-button (npm)

MAL-2026-1818

Immediate action

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

npm uninstall player-button

What this malware does

The package player-button was found to contain malicious code.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

2b24dacca6297698f9b488fdfd210c342c3e0d92c7a9cea39fba3d6ca73725d1

7ef576512d757081a6ffcf3225a09220078dde23b0825b516ee210f6bf1b0c94

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for player-button (version 100.0.0).
If you installed it — respond
Remove player-button 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-button 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-button 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-01495

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks player-button-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