Malicious Code Injection in m-nut-beligoli Package

m-nut-beligoli Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158918: Malicious code in m-nut-beligoli (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The m-nut-beligoli package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a broader campaign that exploits npm's package publishing system. This package is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the m-nut-beligoli package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, which can lead to a compromised npm registry and potential security risks for developers using these packages. The origin of this issue is linked to a campaign aimed at exploiting npm for token rewards, making it a significant concern for the integrity of the ecosystem.

How To Fix

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

npm uninstall m-nut-beligoli

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 m-nut-beligoli package and replace it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The m-nut-beligoli package poses a significant risk due to its embedded malicious code, which can compromise the integrity of the npm registry and affect developers' projects. It is crucial to uninstall this package and monitor your dependencies for any vulnerabilities.

See every vulnerability recorded for m-nut-beligoli →

Share this vulnerability

FAQ

The m-nut-beligoli package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The malicious code modifies your package.json file, removes private flags, and can lead to the continuous republishing of compromised packages, which may affect your project's integrity.

You should uninstall the m-nut-beligoli package immediately and check for any dependencies that may rely on it.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities without needing to access the code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall m-nut-beligoli

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