Which versions of amgularjs are malicious?

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

How do I remediate amgularjs if I installed it?

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

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

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

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

Malicious package

amgularjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7112

Immediate action

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

npm uninstall amgularjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

a8605895225f9f49cad8abef13db0767d3f35644f0fcfa72a551c14a27b43c5d

92f761681fa0e9bc39b6fb8c77824fc7582c38ac4b348938239dd8ff7de1b6bf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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