Which versions of angularss are malicious?

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

How do I remediate angularss if I installed it?

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

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

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

Search your lockfiles and build artifacts for angularss (2 malicious versions).

Malicious package

angularssnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angularss is a confirmed malicious npm package (MAL-2026-7152) that executes malicious code on install (malicious versions 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angularss (npm)

MAL-2026-7152

Immediate action

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

npm uninstall angularss

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

a0ab0d21af0f673454de4e7205b9fc3e0aebc6abb99cc9ea518ef03c864164ca

9931ed33ffc45603b48d255627cee5f916a1c45ddf6b5752b564b284c487efff

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angularss (2 malicious versions).
If you installed it — respond
Remove angularss 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 angularss 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. angularss on npm has been identified as a malicious package (versions 1.1.4, 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04872RLUA-2026-06007

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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