Malicious Code Injection in madrid-u-beligoli: A Threat to npm Packages

madrid-u-beligoli Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159002: Malicious code in madrid-u-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'madrid-u-beligoli' 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.

Vulnerability Detail

The vulnerability in 'madrid-u-beligoli' stems from its association with the tea.xyz token reward campaign, which has been flooding npm with malicious packages. These packages contain scripts designed to modify the package.json file, removing private flags and changing version numbers. They also generate random package names and continuously republish variants, polluting the npm registry. This can lead to compromised developer reputation and potential exploitation of applications relying on these packages.

How To Fix

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

npm uninstall madrid-u-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 measure, you can avoid using the 'madrid-u-beligoli' package and any other packages associated with the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The 'madrid-u-beligoli' package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies. By removing this package and utilizing tools like Vulert, developers can better protect their applications from potential threats.

See every vulnerability recorded for madrid-u-beligoli →

Share this vulnerability

FAQ

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

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

You should uninstall the 'madrid-u-beligoli' package immediately and audit your project for any other potentially malicious dependencies.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall madrid-u-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