Malicious Code Injection in messi-ftfa-sfdsfsuf Package - npm Vulnerability

messi-ftfa-sfdsfsuf Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160319: Malicious code in messi-ftfa-sfdsfsuf (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-sfdsfsuf 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 that aims to exploit npm's publishing mechanisms. It is designed to automatically generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. The presence of this package poses significant risks to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability stems from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.

How To Fix

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

npm uninstall messi-ftfa-sfdsfsuf

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-ftfa-sfdsfsuf package and any other packages that may be part of the same malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The messi-ftfa-sfdsfsuf package poses a significant risk due to its malicious code designed to exploit npm's publishing system. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying vigilant and proactive in managing dependencies can help maintain the security of your applications.

See every vulnerability recorded for messi-ftfa-sfdsfsuf →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing mechanisms.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You can use tools like Vulert to monitor and alert for open-source vulnerabilities in your project. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately using npm uninstall messi-ftfa-sfdsfsuf and check for any lingering references in your package-lock.json file.

Yes, Vulert provides a service that monitors your package-lock.json for vulnerabilities in real-time, helping you stay informed about potential risks.

How To Fix

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

npm uninstall messi-ftfa-sfdsfsuf

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