Malicious Code Injection in samehadaku-messi-cr7 Package

samehadaku-messi-cr7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165723: Malicious code in samehadaku-messi-cr7 (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 samehadaku-messi-cr7 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 deployment 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 numerous derivative packages.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the samehadaku-messi-cr7 package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious scripts (auto.js, autopublish.js, etc.) continuously republish these variants, polluting the npm registry and potentially leading to reputation damage for legitimate developers and security risks for users who inadvertently install these packages.

How To Fix

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

npm uninstall samehadaku-messi-cr7

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 samehadaku-messi-cr7 package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before installation.

Conclusion

The samehadaku-messi-cr7 package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is essential to remove this package from your projects and stay vigilant about the packages you use. Utilizing tools like Vulert can help you maintain the security of your applications.

See every vulnerability recorded for samehadaku-messi-cr7 →

Share this vulnerability

FAQ

The samehadaku-messi-cr7 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

If your application uses the samehadaku-messi-cr7 package, it may inadvertently contribute to the pollution of the npm registry and expose your project to security risks associated with malicious code.

You should immediately uninstall the samehadaku-messi-cr7 package from your project and review your dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software. You can also check your application against vulnerabilities using the Vulert playground without any signup.

Yes, tools like Vulert can help you identify and monitor vulnerabilities in your project dependencies, ensuring that you are alerted to any potential risks.

How To Fix

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

npm uninstall samehadaku-messi-cr7

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