Malicious Code Detected in nnc-web Package - Security Alert

nnc-web Updated 01 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191520: Malicious code in nnc-web (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The nnc-web package is a Node.js library used for web development, providing various functionalities to streamline the creation of web applications. However, it has been identified with a significant security vulnerability that introduces malicious code, potentially compromising applications that utilize this package.

Vulnerability Detail

The vulnerability originates from the discovery of malicious code embedded within the nnc-web package. This code can lead to unauthorized access, data breaches, or other harmful actions within applications that depend on it. The malicious nature of this code poses a severe risk to the integrity and security of affected systems.

How To Fix

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

npm uninstall nnc-web

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

As a temporary workaround, consider removing the nnc-web package from your project until a secure version is available. You can do this by executing: npm uninstall nnc-web.

Conclusion

The nnc-web package has been identified with a serious vulnerability due to the presence of malicious code. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for nnc-web →

Share this vulnerability

FAQ

nnc-web is a Node.js library designed for web development, offering various features to facilitate the creation of web applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected by this vulnerability.

If immediate updates are not feasible, consider removing the nnc-web package as a temporary measure to mitigate risks.

Detailed information about this vulnerability can be found in the official security advisory or through vulnerability databases like Vulert.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall nnc-web

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