Which versions of swplayer-react-sl are malicious?

The following npm versions of swplayer-react-sl are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate swplayer-react-sl if I installed it?

swplayer-react-sl 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 swplayer-react-sl — how do I know if it already compromised me?

If swplayer-react-sl 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 swplayer-react-sl part of a known attack campaign?

Yes — swplayer-react-sl is associated with the GHSA-959p-q4g9-cc8r, RLMA-2026-05328, RLUA-2026-05628 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 swplayer-react-sl 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 swplayer-react-sl (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging swplayer-react-sl across your stack and pipelines.

Malicious package

swplayer-react-slnpm

swplayer-react-sl is a confirmed malicious npm package (MAL-2026-2906) that opens a backdoor for remote access (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in swplayer-react-sl (npm)

MAL-2026-2906

Immediate action

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

npm uninstall swplayer-react-sl

What this malware does

swplayer-react-sl is a malicious npm package that when imported downloads a C2 dropper from https://coingecko-liard.vercel[.]app and executes it.

The package swplayer-react-sl was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

fb25be00997a0e21d0d5337b89729fe6c3a99c9364f8a46d4b2e2a828e845f54

1e6e1d2ef52b2485c6e3bb83f0af9cd456b7598f6b862c3e7f4bb6ed2fd2fb10

300fd3e7f311d4e659677e2676496fcbab0c27c92166afe3c6181ff14606e9f3

16c722953ecf3d0586f8899c24071fce0d8a1d938eed5519798df067ac8aecfa

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 swplayer-react-sl (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging swplayer-react-sl across your stack and pipelines.
If you installed it — respond
swplayer-react-sl 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 swplayer-react-sl 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 swplayer-react-sl 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. swplayer-react-sl on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-959p-q4g9-cc8rRLMA-2026-05328RLUA-2026-05628

References

Credits

Amazon Inspector · finder
ReversingLabs · finder
indece · finder

Detect & block this

O3 blocks swplayer-react-sl-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