Which versions of mngularjs are malicious?

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

How do I remediate mngularjs if I installed it?

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

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

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

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

Malicious package

mngularjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

mngularjs is a confirmed malicious npm package (MAL-2026-7320) 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 mngularjs (npm)

MAL-2026-7320

Immediate action

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

npm uninstall mngularjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

e17e68b47f6703ea385ad22d641129501340e1c7f069e4f44cc4f569fabf90ce

18328f6de195c3549fdee97f6f29b803e6f9d3312e5153c35fa5c9781566e0ec

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for mngularjs (3 malicious versions).
If you installed it — respond
Remove mngularjs 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 mngularjs 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. mngularjs 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-05160RLUA-2026-06329

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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