Which versions of rngularjs are malicious?

The following npm versions of rngularjs are flagged malicious: 1.1.2, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate rngularjs if I installed it?

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

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

Yes — rngularjs is associated with the RLMA-2026-05297, RLUA-2026-06464 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 rngularjs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rngularjs (3 malicious versions).

Malicious package

rngularjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

rngularjs is a confirmed malicious npm package (MAL-2026-7404) that executes malicious code on install (malicious versions 1.1.2, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rngularjs (npm)

MAL-2026-7404

Immediate action

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

npm uninstall rngularjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

419980e9c01baf4a90623ccb45908ce5efb3531fbdfb7acbf8700a70d1aa0215

2febe5e5f4332869746fa788088df8bcf2a1ad3b2f38f8646874b316c1b7ac69

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05297RLUA-2026-06464

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks rngularjs-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