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

@oku-ui/alert-dialognpm

Malicious code in @oku-ui/alert-dialog (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191248
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @oku-ui/alert-dialog

What this malware does

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

be18562e644d3f0124c350905e24f5fe4edcf3c4198cfc4a50dc9e15d2e9306e
824a69f83431a766f681bc72d705ff3b28ae9309898b4ad10979adca148f2276

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 @oku-ui/alert-dialog (version 0.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @oku-ui/alert-dialog across your stack and pipelines.

  2. If you installed it — respond

    @oku-ui/alert-dialog 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 @oku-ui/alert-dialog 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 @oku-ui/alert-dialog 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. @oku-ui/alert-dialog 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/alert-dialog-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

@oku-ui/alert-dialog (npm) malicious package — MAL-2025-191248 | O3 Security