Which versions of @oku-ui/avatar are malicious?

The following npm versions of @oku-ui/avatar are flagged malicious: 0.6.2. Treat any of these as compromised.

How do I remediate @oku-ui/avatar if I installed it?

@oku-ui/avatar 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.

I already installed @oku-ui/avatar — how do I know if it already compromised me?

If @oku-ui/avatar 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 @oku-ui/avatar across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @oku-ui/avatar (version 0.6.2).

Part of a larger attack: @oku-ui published 43 malicious packages. See the full campaign →

Malicious package

@oku-ui/avatarnpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@oku-ui/avatar is a confirmed malicious npm package (MAL-2025-191251) that steals credentials and exfiltrates sensitive data (malicious version 0.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @oku-ui/avatar (npm)

MAL-2025-191251

Immediate action

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

npm uninstall @oku-ui/avatar

What this malware does

The package @oku-ui/avatar was found to contain malicious code.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.6.2

Indicators of compromise (SHA-256)

2f6bd71861c49a57e029ac8503356e0acf600a6fa86dd9a0d47e8c42fd660425

23d026f94dcbe031cd4e8c72102d71358e1909bb7b14a95645e7fd46d955e0c9

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @oku-ui/avatar (version 0.6.2).
If you installed it — respond
@oku-ui/avatar 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.
Did it already run?
If @oku-ui/avatar 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. @oku-ui/avatar on npm has been identified as a malicious package (version 0.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @oku-ui/avatar-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database