Which versions of webnochs are malicious?

Every published version of webnochs on npm is considered malicious. Remove the package entirely.

How do I remediate webnochs if I installed it?

Remove webnochs 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 webnochs — how do I know if it already compromised me?

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

Yes — webnochs is associated with the GHSA-ccvh-6226-jf5g 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 webnochs 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 webnochs (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging webnochs across your stack and pipelines.

Malicious package

webnochsnpm

Malicious code in webnochs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1181

Immediate action

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

npm uninstall webnochs

What this malware does

The package webnochs 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

254c459dafb2f3949b0e8cf6c70e4faa60aa14c46866879b8e80185bf07d89c8

0860fbeb548c9d3b4715f96f79662f1dc2bd03a179268a2aba3dd907a7fa7a1b

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

Campaign

GHSA-ccvh-6226-jf5g

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks webnochs-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