Which versions of kc-next are malicious?

The following npm versions of kc-next are flagged malicious: 2.3.2. Treat any of these as compromised.

How do I remediate kc-next if I installed it?

Remove kc-next from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed kc-next — how do I know if it already compromised me?

If kc-next 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 kc-next part of a known attack campaign?

Yes — kc-next is associated with the GHSA-cmmm-3vrh-vj98 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 kc-next 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 kc-next (version 2.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kc-next across your stack and pipelines.

Malicious package

kc-nextnpm

Malicious code in kc-next (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190574

Immediate action

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

npm uninstall kc-next

What this malware does

The package kc-next 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.

The OpenSSF Package Analysis project identified 'kc-next' @ 2.3.2 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

2.3.2

Indicators of compromise (SHA-256)

0c63bb1691f831f642b59155524e94597c44a3fb96dbbe7995746c01102e1b24

32088d023faff39ca532f60b6fefa143e98da4ff439ecf1d9922cbb7f5f669ef

750f8ce90382db0d1c42cc21bef3cce0f5220048311c62bff8fb2928e2b936c6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kc-next (version 2.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kc-next across your stack and pipelines.
If you installed it — respond
Remove kc-next from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If kc-next 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 kc-next 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. kc-next on npm has been identified as a malicious package (version 2.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cmmm-3vrh-vj98

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks kc-next-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring