Malicious Code Injection in messi-buysa-1 Package: A Threat to npm Ecosystem

messi-buysa-1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160296: Malicious code in messi-buysa-1 (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-buysa-1 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 distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing features to inflate developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, thereby polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, posing a significant risk to developers relying on npm for legitimate packages.

How To Fix

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

npm uninstall messi-buysa-1

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, you can avoid using the messi-buysa-1 package and replace it with a trusted alternative. Always verify the integrity of packages before installation.

Conclusion

The messi-buysa-1 package poses a significant threat due to its malicious code designed to exploit the npm ecosystem. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard applications from such threats.

See every vulnerability recorded for messi-buysa-1 →

Share this vulnerability

FAQ

messi-buysa-1 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should immediately uninstall the messi-buysa-1 package and check your application for any signs of compromise.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.

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

How To Fix

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

npm uninstall messi-buysa-1

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