Which versions of auth-handler are malicious?

The following npm versions of auth-handler are flagged malicious: 2.5.8. Treat any of these as compromised.

How do I remediate auth-handler if I installed it?

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

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

Yes — auth-handler is associated with the RLMA-2025-06063, RLUA-2026-01112 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 auth-handler across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for auth-handler (version 2.5.8).

Malicious package

auth-handlernpm

Advisory published Dec 23, 2025Updated Mar 19, 2026

auth-handler is a confirmed malicious npm package (MAL-2025-192712) that executes malicious code on install (malicious version 2.5.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in auth-handler (npm)

MAL-2025-192712

Immediate action

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

npm uninstall auth-handler

What this malware does

The package auth-handler was found to contain malicious code.

Malicious versions

1 flagged

2.5.8

Indicators of compromise (SHA-256)

7b1ef6a437d15ff984467bae6811469d0451b0b00fe3b9f2b7a43da5a15e6556

79d1be042f1565157d9c5e97b927919aa32bedb254b501aa374caf00c242ee83

c7d7c686621c8937d5938b503be6a128aae85c1644121878ec5e5b30fb98c03e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06063RLUA-2026-01112

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks auth-handler-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