Malicious Code Injection in munisdr-nserf-sad Package: npm Vulnerability Alert

munisdr-nserf-sad Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160952: Malicious code in munisdr-nserf-sad (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 munisdr-nserf-sad package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to significant security risks.

Vulnerability Detail

The vulnerability in the munisdr-nserf-sad package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can lead to the installation of compromised packages, potentially exposing applications to further vulnerabilities.

How To Fix

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

npm uninstall munisdr-nserf-sad

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, avoid using the munisdr-nserf-sad package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The munisdr-nserf-sad package poses a significant security risk due to its malicious code that modifies package configurations and floods the npm registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications remain secure.

See every vulnerability recorded for munisdr-nserf-sad →

Share this vulnerability

FAQ

The munisdr-nserf-sad package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

If your application uses the munisdr-nserf-sad package, it may be at risk of installing compromised packages that can lead to further vulnerabilities and security breaches.

You should immediately uninstall the munisdr-nserf-sad package using npm uninstall munisdr-nserf-sad and audit your project for any other potentially compromised packages.

You can use tools like npm audit to check for vulnerabilities in your dependencies. Additionally, services like Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup or installation.

How To Fix

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

npm uninstall munisdr-nserf-sad

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