Which versions of anjularjs are malicious?

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

How do I remediate anjularjs if I installed it?

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

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

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

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

Malicious package

anjularjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7205

Immediate action

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

npm uninstall anjularjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

0db4cdd6e0079f5269368e78d02a1ec7b381891bfc4240725450ea1f233a3311

c98097075ab7657a4e84ef5796f24757ec9d31cae4d177792b5804613928052e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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