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

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

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

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

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

Is @oku-ui/slot part of a known attack campaign?

Yes — @oku-ui/slot is associated with the GHSA-4qrx-3m9c-5qv4 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @oku-ui/slot across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @oku-ui/slot (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/slot across your stack and pipelines.

Malicious package

@oku-ui/slotnpm

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

MAL-2025-191042

Immediate action

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

npm uninstall @oku-ui/slot

What this malware does

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

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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)

2a90589b3706323fe3b284df0f3935425b573427c0e51600a8c59a2fc69a670d

090f061e5efc93843291952e02c0a05f32a22893162dfeffc54c3ec504135422

c00107e442d452bcb43403d89ade38e4fb111f1d1624b2dc4d2498df1f9a6ca2

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @oku-ui/slot (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/slot across your stack and pipelines.
If you installed it — respond
@oku-ui/slot 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/slot 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.
How O3 protects you
O3 blocks @oku-ui/slot 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/slot 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.

Campaign

GHSA-4qrx-3m9c-5qv4

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @oku-ui/slot-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