Which versions of angularps are malicious?

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

How do I remediate angularps if I installed it?

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

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

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

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

Malicious package

angularpsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7150

Immediate action

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

npm uninstall angularps

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

0e9731dcdf219341c8a8f57144956bc695d9b479ae8866c494de0d146e843022

0474173b23ce9a5a93798783a32ead70cce94c42a2895e0cfc4f20204230a172

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angularps (2 malicious versions).
If you installed it — respond
Remove angularps 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 angularps 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. angularps 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-04870RLUA-2026-06005

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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