Malicious Code Injection in messi-urat-efduds Package

messi-urat-efduds Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160387: Malicious code in messi-urat-efduds (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 messi-urat-efduds package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious code that modifies package configurations and publishes variants to the npm registry, leading to potential security risks.

Vulnerability Detail

The vulnerability in the messi-urat-efduds package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to security risks from untrusted code.

How To Fix

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

npm uninstall messi-urat-efduds

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-efduds package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.

Conclusion

The messi-urat-efduds package has been identified as containing malicious code that poses significant risks to developers and their projects. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for messi-urat-efduds →

Share this vulnerability

FAQ

The messi-urat-efduds package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, making it challenging to find legitimate packages and potentially exposing your project to untrusted code.

If you have installed the messi-urat-efduds package, you should uninstall it immediately using the command npm uninstall messi-urat-efduds.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. It requires only the package-lock.json file to provide real-time alerts.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall messi-urat-efduds

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