Which versions of angulbrjs are malicious?

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

How do I remediate angulbrjs if I installed it?

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

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

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

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

Malicious package

angulbrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7163

Immediate action

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

npm uninstall angulbrjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

1493708f97c1c5b5fa079ede7f5c92353ac00fe80ce775cca45d09730431b4ad

dacc8b8033c583d3b262eb1bb11ea0dcd53cee8431b7ea71a0b306cd4d176506

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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