Which versions of kns-error-code are malicious?

The following npm versions of kns-error-code are flagged malicious: 1.0.8. Treat any of these as compromised.

How do I remediate kns-error-code if I installed it?

kns-error-code 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 kns-error-code — how do I know if it already compromised me?

If kns-error-code 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 kns-error-code part of a known attack campaign?

Yes — kns-error-code is associated with the GHSA-8x3r-8fmv-7cm4 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 kns-error-code 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 kns-error-code (version 1.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kns-error-code across your stack and pipelines.

Malicious package

kns-error-codenpm

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

MAL-2025-191120

Immediate action

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

npm uninstall kns-error-code

What this malware does

The package kns-error-code 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

1.0.8

Indicators of compromise (SHA-256)

bfbb83f30dda5940166bed636d96b2ffa93059f5380ee5d90a3e6310346f0a66

8b5cf5bab2739281bad9ad42a645dbd6f01c9a23befedf22e0c86913a4a024aa

800f2a399cfa77f8709d51ca0a8025493c82b93ea829c48a471cf175090104b0

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

Campaign

GHSA-8x3r-8fmv-7cm4

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks kns-error-code-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