Which versions of angularfs are malicious?

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

How do I remediate angularfs if I installed it?

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

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

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

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

Malicious package

angularfsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7143

Immediate action

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

npm uninstall angularfs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

41f1602a01e00c88f80add50f73971f676fe979be89042a6ec2082817366c3c5

080af5ed4674164f5e8a8e82f5861a9adb535dbe97d86699abfa1f9b109764c4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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