Which versions of encounter-playground are malicious?

The following npm versions of encounter-playground are flagged malicious: 0.0.2, 0.0.3, 0.0.4, 0.0.5. Treat any of these as compromised.

How do I remediate encounter-playground if I installed it?

encounter-playground is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed encounter-playground — how do I know if it already compromised me?

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

Yes — encounter-playground is associated with the GHSA-6hv4-r5mw-55vr, RLMA-2025-04993, RLUA-2025-05354, RLUA-2025-05776 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 encounter-playground 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 encounter-playground (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging encounter-playground across your stack and pipelines.

Malicious package

encounter-playgroundnpm

encounter-playground is a confirmed malicious npm package (MAL-2025-47312) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.2, 0.0.3, 0.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in encounter-playground (npm)

MAL-2025-47312

Immediate action

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

npm uninstall encounter-playground

What this malware does

The package was compromised and malicious code added.

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.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

4 flagged

0.0.20.0.30.0.40.0.5

Indicators of compromise (SHA-256)

e60b1e5e20cf97dc1520f1bc748ccea5054513b4d6cef4117655810541013d7c

35d3ddc34a0f116ae7603d80015647e487a0703aee6ed2f42609f6dc3a875ae5

9e8c0be58c8456987261fed272e225d4b9249356a9c76f6806679b5d69bf5673

c5e59507f2c9550695fa15837e0e46f9f80978e0b859f1a694de4df51c9b0ad7

771fef23185504514bdc7cafd34a43e36b32343f7f929ef9af14704fdc0d45ba

3261d9f555dbf2cb69ccb6a270eb2b62b4bb5e8b748db64726d58998eddd2b66

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for encounter-playground (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging encounter-playground across your stack and pipelines.
If you installed it — respond
encounter-playground is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If encounter-playground 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 encounter-playground 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. encounter-playground on npm has been identified as a malicious package (versions 0.0.2, 0.0.3, 0.0.4, 0.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6hv4-r5mw-55vrRLMA-2025-04993RLUA-2025-05354RLUA-2025-05776

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks encounter-playground-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database