Which versions of player-common-composites are malicious?

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

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

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

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

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

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

Malicious package

player-common-compositesnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

player-common-composites is a confirmed malicious npm package (MAL-2026-1819) 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-composites (npm)

MAL-2026-1819

Immediate action

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

npm uninstall player-common-composites

What this malware does

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

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

259a11b1064d2752d236e14516879786e7c141d0f68a590219117db74e7ddd66

4455f92c445aa0e00604813f2b53943a2ce8b7866175fcb84ab7bcd867f65f70

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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