Which versions of angusarjs are malicious?

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

How do I remediate angusarjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for angusarjs (2 malicious versions).

Malicious package

angusarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angusarjs is a confirmed malicious npm package (MAL-2026-7192) that executes malicious code on install (malicious versions 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angusarjs (npm)

MAL-2026-7192

Immediate action

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

npm uninstall angusarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

d8efad596e061abd23b171ec6340c8fc7cc1e28a32951c6d5c56529741114963

a18750a4cf843a37ad43177399237b426b54fcbe515c2bb9f78017860fdfbdfe

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angusarjs (2 malicious versions).
If you installed it — respond
Remove angusarjs 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 angusarjs 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. angusarjs on npm has been identified as a malicious package (versions 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-04912RLUA-2026-06047

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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