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

rules-deployernpm

Advisory published Updated

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

Malicious code in rules-deployer (npm)

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

What this malware does

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

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

It is considered malicious because:

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

Malicious versions

1 flagged
0.0.0

Indicators of compromise (SHA-256)

c4db6440dc23c5dddffabd81ff195cbea3783192fe2d62d25402ac3c8f1f4699
849a58d27ed0090633a72330c705b5849146aa1493961574c6a11dc758e28e34

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for rules-deployer (version 0.0.0).

  2. If you installed it — respond

    Remove rules-deployer 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-deployer 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-deployer on npm has been identified as a malicious package (version 0.0.0 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-deployer-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-deployer (npm) malicious package — MAL-2026-3 | O3 Security