Malicious Code Injection in badruddin Package: npm Vulnerability Alert

badruddin Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170947: Malicious code in badruddin (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 badruddin package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to manage dependencies in their projects. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing features, leading to potential security risks for users and their applications.

Vulnerability Detail

The vulnerability in the badruddin package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the developer's reputation and can lead to unintended consequences in applications that depend on these packages.

How To Fix

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

npm uninstall badruddin

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, you can avoid using the badruddin package and instead look for alternative packages that provide similar functionality without the associated risks. Always review the packages you intend to use for any signs of malicious behavior.

Conclusion

The badruddin package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity and security of their applications. Utilizing tools like Vulert can help in monitoring for similar vulnerabilities in the future.

See every vulnerability recorded for badruddin →

Share this vulnerability

FAQ

The badruddin package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

This vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the badruddin package immediately using 'npm uninstall badruddin' and check for any dependencies that may also be affected.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

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 badruddin

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