Malicious Code Injection in messi-ftfa-fdasuf Package: A Threat to npm Users

messi-ftfa-fdasuf Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160316: Malicious code in messi-ftfa-fdasuf (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 messi-ftfa-fdasuf 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 and deployment 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 risks for developers and users alike.

Vulnerability Detail

The vulnerability stems from the messi-ftfa-fdasuf package being associated with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers.

How To Fix

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

npm uninstall messi-ftfa-fdasuf

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, avoid using the messi-ftfa-fdasuf package and monitor your package-lock.json file for any unauthorized changes. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The messi-ftfa-fdasuf package poses a significant security risk due to its association with a malicious campaign targeting npm users. It is essential to remove this package from your projects, monitor your dependencies, and utilize tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for messi-ftfa-fdasuf →

Share this vulnerability

FAQ

The messi-ftfa-fdasuf package is an npm package that has been identified as part of a malicious campaign aimed at exploiting npm's publishing system.

This vulnerability can lead to the installation of malicious code, compromising your application and potentially exposing sensitive data.

If you have installed the messi-ftfa-fdasuf package, you should uninstall it immediately and audit your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your dependencies.

How To Fix

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

npm uninstall messi-ftfa-fdasuf

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