Malicious Code Injection in madri-nut-beligoli Package

madri-nut-beligoli Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158999: Malicious code in madri-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 madri-nut-beligoli package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages designed to manipulate npm's package registry. This package, like others in the campaign, is engineered to inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the madri-nut-beligoli package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which aims to exploit npm's registry by flooding it with numerous derivative packages. The ramifications include potential security risks for developers using this package, as it can lead to reputation damage and misuse of the npm registry.

How To Fix

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

npm uninstall madri-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, consider removing the madri-nut-beligoli package from your project until a secure version is released. You can do this by executing: npm uninstall madri-nut-beligoli. Additionally, monitor your package-lock.json file for any unexpected changes.

Conclusion

The madri-nut-beligoli package contains malicious code that poses significant risks to developers and their applications. Immediate action is required to mitigate these risks by updating or removing the package. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for madri-nut-beligoli →

Share this vulnerability

FAQ

The madri-nut-beligoli package is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.

If you are using the madri-nut-beligoli package, it is recommended to uninstall it immediately and monitor for any updates or patches.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application at Vulert Scanner.

Long-term implications include potential security breaches, reputation damage for developers, and the risk of further exploitation of the npm registry.

How To Fix

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

npm uninstall madri-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