Which versions of angulfrjs are malicious?

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

How do I remediate angulfrjs if I installed it?

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

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

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

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

Malicious package

angulfrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7167

Immediate action

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

npm uninstall angulfrjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

400995bcb95d210889586926da17dd6e478d63485cf5aa8a522dad310720f671

c68f8080c74abc7fb0c1978ef4228b98bc4b5abb8e025e90e3bfb36affa84988

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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