Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

unisys-ukanpm

Malicious code in unisys-uka (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2824
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall unisys-uka

What this malware does

Package is malware. Collects sensitive info, reads files, executes commands, and exfiltrates data to a remote server via postinstall script.

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

The OpenSSF Package Analysis project identified 'unisys-uka' @ 99.99.1 (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.1

Indicators of compromise (SHA-256)

f587bf8cae0a6838cff256b7a3a34295dc751390dcb7a9807ce353aaea5218ff
25745bb1be4d673e8e465091f55bfdad6ad5cd5740583fd9a9f38fd7dd3e5d57

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for unisys-uka (version 99.99.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unisys-uka across your stack and pipelines.

  2. If you installed it — respond

    unisys-uka is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If unisys-uka was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks unisys-uka before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. unisys-uka on npm has been identified as a malicious package (version 99.99.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • SafeDep · finder

Detect & block this

O3 blocks unisys-uka-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

unisys-uka (npm) malicious package — MAL-2026-2824 | O3 Security