Malicious Code Injection in messi-urat-disa Package: A Threat to npm Users

messi-urat-disa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160384: Malicious code in messi-urat-disa (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 messi-urat-disa package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at exploiting npm's publishing capabilities. It is designed to generate and publish derivative packages with randomized names, ultimately inflating developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in the messi-urat-disa package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is indicative of a broader scheme to pollute the npm registry with derivative packages, which can lead to security risks, including the potential for unauthorized access to sensitive data or the execution of harmful scripts. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been flooding the npm registry with such malicious packages.

How To Fix

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

npm uninstall messi-urat-disa

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 messi-urat-disa 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 without requiring code access or installation.

Conclusion

The messi-urat-disa package poses a significant threat due to its malicious code designed to manipulate npm's publishing process. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your projects from potential risks associated with malicious packages.

See every vulnerability recorded for messi-urat-disa →

Share this vulnerability

FAQ

The messi-urat-disa package is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing features.

The vulnerability can lead to unauthorized modifications in your project, potentially exposing sensitive data or executing harmful scripts.

You should uninstall the messi-urat-disa package immediately and monitor your project for any unauthorized changes.

You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities and receive real-time alerts.

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

How To Fix

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

npm uninstall messi-urat-disa

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