Which versions of angularos are malicious?

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

How do I remediate angularos if I installed it?

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

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

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

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

Malicious package

angularosnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7149

Immediate action

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

npm uninstall angularos

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

bdb4f83e3a64e38c20adb81de1e20e9857032b335c8206e9d3ad46290016315c

a7a80907c16bd619500312ca5aa2dd5d8c42634efb36df799bc0288925b66b2e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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