Which versions of angularhs are malicious?

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

How do I remediate angularhs if I installed it?

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

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

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

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

Malicious package

angularhsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7145

Immediate action

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

npm uninstall angularhs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

8d8c3c871b6ac1435bb87abfb2d8fbec9df2771d820680fe4cf392713e755976

d779247240e3d189b6176fe2fd56355751619646e8bbc72ad78a743060069617

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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