Which versions of unisys-auth are malicious?

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

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

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

If unisys-auth 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.

How do I find unisys-auth across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for unisys-auth (version 99.99.2).

Malicious package

unisys-authnpm

Advisory published Apr 11, 2026Updated Apr 23, 2026

unisys-auth is a confirmed malicious npm package (MAL-2026-2875) that executes malicious code on install (malicious version 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in unisys-auth (npm)

MAL-2026-2875

Immediate action

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

npm uninstall unisys-auth

What this malware does

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

The OpenSSF Package Analysis project identified 'unisys-auth' @ 99.99.2 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.99.2

Indicators of compromise (SHA-256)

c5f6e845dfc93eebade7f512b7f0594f0d3678dc827762a5d5eccbfaa7f0f0ff

89bc257f69dca8cec54b15b47533c97f9b6b47f16aae5f2dc868ff7faaf0c93b

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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