Critical Malicious Code Vulnerability in duverger Package

duverger Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19000: Malicious code in duverger (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 duverger package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various purposes, including data manipulation and web development tasks. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the duverger package originates from the inclusion of malicious code, which can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the duverger package, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall duverger

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 replacing the duverger package with an alternative library that offers similar functionality without the associated risks. Review your project's dependencies and assess other npm packages that can fulfill the same role safely.

Conclusion

The discovery of malicious code in the duverger package highlights the importance of maintaining secure dependencies in software development. Developers are urged to remove the affected package and monitor for updates or alternatives to ensure the safety of their applications.

See every vulnerability recorded for duverger →

Share this vulnerability

FAQ

The duverger package is used in JavaScript applications for various functionalities, including data manipulation and web development tasks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without needing to sign up.

If immediate removal is not possible, consider replacing it with a safer alternative while you work on a more permanent solution.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

Regularly check your project's dependencies and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall duverger

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