Critical Malicious Code Vulnerability in webnoch Package

webnoch Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1180: Malicious code in webnoch (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The webnoch package is an npm library designed for web development, providing various functionalities that enhance the user experience. However, it has been identified to contain malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and users alike, as it can lead to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the webnoch package, identified by the alias GHSA-gp8w-96qw-8c33. Any system running this package is considered fully compromised, with all stored secrets and keys at risk. The malicious code can allow external entities to gain full control over the affected computer, making it imperative for users to take immediate action.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall webnoch

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, the only effective workaround is to uninstall the webnoch package. Use the following command in your terminal: npm uninstall webnoch. This action will help mitigate the risk, but be aware that full control may have already been compromised.

Conclusion

The webnoch package has been identified as containing malicious code that poses a severe security risk. Users are advised to uninstall the package immediately and take necessary precautions to secure their systems. Monitoring tools like Vulert can assist in identifying vulnerabilities in your software.

See every vulnerability recorded for webnoch →

Share this vulnerability

FAQ

webnoch is an npm package used for web development, offering various functionalities to enhance user experience.

The malicious code can grant unauthorized access to external entities, compromising the security of your system and data.

Immediately uninstall the webnoch package and rotate all secrets and keys stored on your system.

As of now, there is no patch available. The best course of action is to remove the package entirely.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall webnoch

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback