Which versions of angulafjs are malicious?

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

How do I remediate angulafjs if I installed it?

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

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

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

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

Malicious package

angulafjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7129

Immediate action

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

npm uninstall angulafjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

353001bfe925c9c13474f269e2adf32df3878e841a6cd10bc35422279e5b9ce2

ad0def5af12a55cc6e454afee148e1e0d5f7fa988cee7be18289df4020b74108

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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