Which versions of pru-lib-ng are malicious?

The following npm versions of pru-lib-ng are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate pru-lib-ng if I installed it?

Remove pru-lib-ng 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 pru-lib-ng — how do I know if it already compromised me?

If pru-lib-ng 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 pru-lib-ng part of a known attack campaign?

Yes — pru-lib-ng is associated with the RLMA-2026-01515 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 pru-lib-ng across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pru-lib-ng (version 9.9.9).

Malicious package

pru-lib-ngnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

pru-lib-ng is a confirmed malicious npm package (MAL-2026-1829) that executes malicious code on install (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pru-lib-ng (npm)

MAL-2026-1829

Immediate action

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

npm uninstall pru-lib-ng

What this malware does

The package pru-lib-ng was found to contain malicious code.

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

b164911ad8cbcbe1e86262e8e14d5d9d6a2371ce51f2dd25da35bd2a49af7bc3

23f37bedfc6e1d85a81c4656a0af7b09fd927fb8d1562702d8766104ba806d95

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pru-lib-ng (version 9.9.9).
If you installed it — respond
Remove pru-lib-ng 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 pru-lib-ng 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. pru-lib-ng on npm has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01515

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pru-lib-ng-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