Which versions of @kvytech/components are malicious?

The following npm versions of @kvytech/components are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate @kvytech/components if I installed it?

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

If @kvytech/components 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 @kvytech/components part of a known attack campaign?

Yes — @kvytech/components is associated with the GHSA-g8xr-cv65-xx89 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 @kvytech/components 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 @kvytech/components (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @kvytech/components across your stack and pipelines.

Malicious package

@kvytech/componentsnpm

Malicious code in @kvytech/components (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190743

Immediate action

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

npm uninstall @kvytech/components

What this malware does

The package @kvytech/components 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.0.2

Indicators of compromise (SHA-256)

f91d56525ec010c618ce55a7c3f942694eb2befa042cf8129208a5dd98ad8615

d1e27717d96aa14c260a48ca84c38f3f08f6b3352f82cd27b83ac56547c46cc6

2d8f12d88763482f30143c412ae8dda0af055c8b18088650530ff9816676af15

5ba99f8e5c2317898f69d890d29f8b4fdae6fd08763cf54416d224794fbf2d47

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

Campaign

GHSA-g8xr-cv65-xx89

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @kvytech/components-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