Malicious Code Injection in messi-tuedda-rtaa Package: A Threat to npm Users

messi-tuedda-rtaa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160366: Malicious code in messi-tuedda-rtaa (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The messi-tuedda-rtaa package 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 aims to exploit the npm registry by flooding it with derivative packages, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in the messi-tuedda-rtaa package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to manipulate developer reputation scores and pollute the npm registry. This poses significant risks, including the potential for developers to unknowingly install compromised packages, leading to security breaches in their applications.

How To Fix

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

npm uninstall messi-tuedda-rtaa

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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the package and avoiding its installation. Always verify the integrity of packages before adding them to your project.

Conclusion

The messi-tuedda-rtaa package represents a significant threat to the npm ecosystem due to its malicious intent to manipulate the registry and compromise developer projects. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for messi-tuedda-rtaa →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with compromised packages.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the messi-tuedda-rtaa package immediately using 'npm uninstall messi-tuedda-rtaa' and review your project for any other potentially compromised packages.

Yes, using npm packages can pose risks if the packages are not from trusted sources, as they may contain malicious code that can compromise your application.

Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from reputable sources.

How To Fix

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

npm uninstall messi-tuedda-rtaa

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