Which versions of angubarjs are malicious?

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

How do I remediate angubarjs if I installed it?

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

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

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

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

Malicious package

angubarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7114

Immediate action

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

npm uninstall angubarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

1ee1fc0768fee909a6cf6f3f610e22ba2e33b557acef8a42ef9c4e234bf4a08c

dba51317b863b3013ee49421db676cf726db817b4c546c56c12857b85775c9de

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angubarjs (2 malicious versions).
If you installed it — respond
Remove angubarjs 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 angubarjs 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. angubarjs 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-04834RLUA-2026-05969

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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