Which versions of angulaxjs are malicious?

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

How do I remediate angulaxjs if I installed it?

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

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

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

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

Malicious package

angulaxjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7160

Immediate action

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

npm uninstall angulaxjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

67793f72fa17ba21dae9a0c93a011536c31a31ffee2803ae5aff4bee2961b269

bafe90580158f3301d08738d422931a22e4c1f010144eb528ec6606f83dff59c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angulaxjs (version 8.7.6).
If you installed it — respond
Remove angulaxjs 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 angulaxjs 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. angulaxjs 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-04880RLUA-2026-06015

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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