Critical Malicious Code Vulnerability in module-listener Package

module-listener Updated 05 Dec 2025

Summary

05/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192308: Malicious code in module-listener (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 module-listener package is a Node.js library used for managing and listening to events in applications. It is designed to facilitate communication between different parts of an application by providing an event-driven architecture. However, this package has been compromised, leading to severe security risks for any application that utilizes it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the module-listener package. This code can grant unauthorized access to the system, potentially compromising all data and secrets stored on the affected machine. The malicious nature of this code means that any system running this package should be considered fully compromised, and immediate action is required to mitigate the risks associated with it.

How To Fix

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

npm uninstall module-listener

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 workaround, if you need similar functionality, consider using alternative packages that provide event-listening capabilities without the associated risks. Always ensure to review the security status of any package before installation.

Conclusion

The module-listener package has been identified as containing malicious code, posing significant security risks to any system using it. Immediate removal of the package and rotation of sensitive information is crucial to mitigate these risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for module-listener →

Share this vulnerability

FAQ

Immediately uninstall the module-listener package using 'npm uninstall module-listener' and rotate any sensitive information stored on the affected machine.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Failing to remove the module-listener package can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Yes, there are several alternative packages available that provide similar event-listening functionality. Always ensure to check their security status before use.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and always review the security history of packages before integrating them into your projects.

How To Fix

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

npm uninstall module-listener

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