Malicious Code Injection in messi-butsa-tusa: npm Package Vulnerability

messi-butsa-tusa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160295: Malicious code in messi-butsa-tusa (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'messi-butsa-tusa' 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms to inflate developer reputation scores through the creation of derivative packages.

Vulnerability Detail

The vulnerability in 'messi-butsa-tusa' arises from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to pollute the npm registry and can lead to security risks for developers who unknowingly use these compromised packages. The malicious payload can also create a chain reaction, affecting other packages and applications that depend on it.

How To Fix

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

npm uninstall messi-butsa-tusa

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-butsa-tusa' package and replace it with a trusted alternative. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The 'messi-butsa-tusa' package poses a significant security risk due to its malicious code injection. It is essential for developers to be vigilant about the packages they use and to regularly audit their dependencies to protect their applications from vulnerabilities. By following the recommended steps to uninstall this package and utilizing tools like Vulert, developers can enhance their security posture.

See every vulnerability recorded for messi-butsa-tusa →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

Using this package can lead to security risks, including the potential for your application to be compromised or polluted with malicious code.

You should uninstall the package immediately using 'npm uninstall messi-butsa-tusa' and review your dependencies for any other potentially harmful packages.

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

Yes, always look for well-reviewed and widely used packages in the npm registry, and ensure they have a good reputation before integrating them into your project.

How To Fix

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

npm uninstall messi-butsa-tusa

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