NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

rules-playgroundnpm

Advisory published Updated

rules-playground is a confirmed malicious npm package (MAL-2026-4) that executes malicious code on install (malicious version 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rules-playground (npm)

MAL-2026-4
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rules-playground

What this malware does

The package rules-playground was found to contain malicious code.

The OpenSSF Package Analysis project identified 'rules-playground' @ 0.0.3 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
0.0.3

Indicators of compromise (SHA-256)

25f6cc3039b9ea0289071ff13147621de7ac3612f749b115ad9ebba1a681d97e
c0cd14651deea0e986dc2d7f9b11494d8c96a074ed9112aaa16076ea19b2b718

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for rules-playground (version 0.0.3).

  2. If you installed it — respond

    Remove rules-playground 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.

  3. Did it already run?

    If rules-playground 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. rules-playground on npm has been identified as a malicious package (version 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks rules-playground-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.

Explore

rules-playground (npm) malicious package — MAL-2026-4 | O3 Security