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

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

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

@oku-ui/popper 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/popper — how do I know if it already compromised me?

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

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

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

Malicious package

@oku-ui/poppernpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@oku-ui/popper is a confirmed malicious npm package (MAL-2025-191263) 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/popper (npm)

MAL-2025-191263

Immediate action

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

npm uninstall @oku-ui/popper

What this malware does

The package @oku-ui/popper 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)

d5145cc0a3483851bce8d5b45c61b4656b80db82046b8b19e0a6069227c10867

c757bdb980fe7035718ca706928b603973b5cc84bc5d18fbe3ab776cbd44e149

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @oku-ui/popper (version 0.6.2).
If you installed it — respond
@oku-ui/popper 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/popper 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/popper 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/popper-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