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

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

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

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

If @oku-ui/primitives 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/primitives part of a known attack campaign?

Yes — @oku-ui/primitives is associated with the GHSA-vg47-hfgj-8573 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/primitives 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/primitives (version 0.7.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @oku-ui/primitives across your stack and pipelines.

Malicious package

@oku-ui/primitivesnpm

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

MAL-2025-191041

Immediate action

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

npm uninstall @oku-ui/primitives

What this malware does

The package @oku-ui/primitives 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.7.9

Indicators of compromise (SHA-256)

55dbe80b72b5112717f8514554db1095334e0757ce7416dde0e77abecb3cfd46

4c4a74bdb0ea1f1f1b9092b53d680498e7f3a43abb1930355d1fab8a49840264

48684386017546a6d1cc3afd6317d995fe7edc730db2789b79af9135d8f88191

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/primitives (version 0.7.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @oku-ui/primitives across your stack and pipelines.
If you installed it — respond
@oku-ui/primitives 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/primitives 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/primitives 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/primitives on npm has been identified as a malicious package (version 0.7.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vg47-hfgj-8573

References

Credits

Amazon Inspector · finder

Detect & block this

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