Critical Malicious Code Vulnerability in js-nodecat Package

js-nodecat Updated 02 Mar 2026

Summary

02/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1116: Malicious code in js-nodecat (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The js-nodecat package is a Node.js library designed for creating chat applications using the Node.js environment. It provides functionalities for managing user interactions and message handling. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and users alike.

Vulnerability Detail

The vulnerability in the js-nodecat package is characterized by the presence of embedded malicious code. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is traced back to the package's malicious code, which poses severe risks to the integrity and confidentiality of the affected systems. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall js-nodecat

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, there are no effective workarounds to mitigate the risks associated with the js-nodecat package. The only recommended action is to uninstall the package entirely.

Conclusion

The js-nodecat package contains critical malicious code that poses a severe security risk to any system it is installed on. Immediate uninstallation of the package and rotation of sensitive information is essential to mitigate the threat. Users should remain vigilant and consider using tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for js-nodecat →

Share this vulnerability

FAQ

js-nodecat is a Node.js library used for building chat applications, providing features for user management and message handling.

The malicious code can fully compromise your system, allowing attackers to access sensitive information and potentially control your computer.

You should uninstall the js-nodecat package immediately and rotate any sensitive information stored on your system.

No, there is currently no patched version available for the js-nodecat package.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities. You can also check your application against vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall js-nodecat

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