Malicious Code Injection in messi-buysa-butsa Package

messi-buysa-butsa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160299: Malicious code in messi-buysa-butsa (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-butsa package is part of a broader ecosystem on npm, often associated with token reward campaigns. These packages are designed to generate and publish derivative versions automatically, which can inflate developer reputation scores. However, this functionality has been exploited, leading to the introduction of malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the messi-buysa-butsa package, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for unauthorized access to sensitive data and the degradation of the npm ecosystem.

How To Fix

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

npm uninstall messi-buysa-butsa

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-butsa package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert to receive alerts for any open-source vulnerabilities.

Conclusion

The messi-buysa-butsa package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for messi-buysa-butsa →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages automatically.

The vulnerability can lead to unauthorized modifications of your package.json file and the potential for malicious code execution within your application.

You can use the Vulert platform to monitor your package-lock.json file for vulnerabilities without needing to install any software.

You should uninstall the package immediately and check for any other dependencies that may have been affected.

Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using just your package-lock.json file.

How To Fix

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

npm uninstall messi-buysa-butsa

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