Malicious Code Injection in messi-buysa-4: A Threat to npm Packages
Summary
MAL-2025-160297: Malicious code in messi-buysa-4 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
messi-buysa-4 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in messi-buysa-4 originates from its involvement in the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The package contains scripts that modify package.json files to remove private flags, change version numbers, and generate random package names. This behavior leads to pollution of the npm registry and can compromise the integrity of the software supply chain, potentially allowing for further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall messi-buysa-4If 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 workaround, you can manually inspect your package-lock.json file to identify and remove any instances of messi-buysa-4. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner.
Conclusion
The messi-buysa-4 package poses a significant threat due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for messi-buysa-4 →
FAQ
messi-buysa-4 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and exposing it to further security risks.
You should remove the messi-buysa-4 package from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by the messi-buysa-4 vulnerability.
