Which versions of anguladjs are malicious?

The following npm versions of anguladjs are flagged malicious: 8.7.6. Treat any of these as compromised.

How do I remediate anguladjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for anguladjs (version 8.7.6).

Malicious package

anguladjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

anguladjs is a confirmed malicious npm package (MAL-2026-7127) that executes malicious code on install (malicious version 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in anguladjs (npm)

MAL-2026-7127

Immediate action

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

npm uninstall anguladjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

f40fb68c1cdd1b8417c92cc0053dd7d431c66c6bd74f36973d9d9704186be98e

017b1338304b7a01d3f4886944f93939a398d5ec7fb45e255ea46f34830f8005

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04847RLUA-2026-05982

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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