Malicious Code Injection in messi-tuas-migtfa: A Threat to npm Users

messi-tuas-migtfa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160348: Malicious code in messi-tuas-migtfa (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'messi-tuas-migtfa' 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 that aims to exploit npm's publishing mechanisms. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names, which can lead to a polluted npm registry.

Vulnerability Detail

The vulnerability in 'messi-tuas-migtfa' originates from its involvement in the tea.xyz token reward campaign. The package contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This malicious behavior allows the package to continuously republish variants, thereby compromising the integrity of the npm registry and potentially affecting users who install these packages.

How To Fix

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

npm uninstall messi-tuas-migtfa

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, avoid using the 'messi-tuas-migtfa' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json file.

Conclusion

The 'messi-tuas-migtfa' package poses a significant risk to npm users due to its malicious code that alters package metadata and republish behavior. It is crucial to uninstall this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for messi-tuas-migtfa →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at exploiting npm's publishing system.

The vulnerability can lead to the installation of malicious packages that may compromise your application's integrity and security.

You should uninstall the package immediately using 'npm uninstall messi-tuas-migtfa' and check your project for any other potentially malicious dependencies.

Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.

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-tuas-migtfa

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