Which versions of angvlarjs are malicious?

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

How do I remediate angvlarjs if I installed it?

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

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

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

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

Malicious package

angvlarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7200

Immediate action

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

npm uninstall angvlarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

9c65d85a90f58ed2635c874ae447d4d385ea571ce8f70f4db9bb21c573a991e2

73a9fbe24bb5fa38aef37e72d5667acbfb548154961fe3f888e83fe64e01026d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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