Critical Malicious Code Vulnerability in enogex Package

enogex Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19665: Malicious code in enogex (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The enogex package is an npm library designed for enhancing Node.js applications with additional functionalities. It is widely used in various projects due to its ease of integration and robust features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The enogex package has been identified to contain malicious code that can compromise the security of applications utilizing it. This vulnerability originated from the package's codebase, which has been tampered with to include harmful scripts. The ramifications of this issue can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. Users are strongly advised to take immediate action to mitigate these risks.

How To Fix

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

npm uninstall enogex

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, users can remove the enogex package from their project until a secure version is confirmed. This can be done using the command: npm uninstall enogex. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The enogex package has been found to contain malicious code, posing serious security risks to applications that use it. Users must take immediate action to update or remove the package to protect their systems. Utilizing tools like Vulert can further enhance security by providing real-time monitoring of open-source vulnerabilities.

See every vulnerability recorded for enogex →

Share this vulnerability

FAQ

The enogex package is an npm library that enhances Node.js applications with additional functionalities.

The malicious code in enogex can lead to unauthorized access and data breaches in applications that utilize it.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

If immediate updates are not possible, consider uninstalling the enogex package and using alternative packages until a secure version is available.

Utilizing tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time, ensuring you are always informed.

How To Fix

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

npm uninstall enogex

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