Which versions of atgularjs are malicious?

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

How do I remediate atgularjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for atgularjs (3 malicious versions).

Malicious package

atgularjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in atgularjs (npm)

MAL-2026-7212

Immediate action

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

npm uninstall atgularjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

ffb76c844d357f8ee80c294aa3cdd74375e46ca1eeb47db842c903bd89cc5ff9

04e7de47b5dbd7903892a0f1f9cb273640586c03d236d815b5272c693ec71319

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for atgularjs (3 malicious versions).
If you installed it — respond
Remove atgularjs 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 atgularjs 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. atgularjs on npm has been identified as a malicious package (versions 1.1.2, 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-04947RLUA-2026-06073

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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