Malicious Code Injection in samehada-zs-r7 Package

samehada-zs-r7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165721: Malicious code in samehada-zs-r7 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The samehada-zs-r7 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a broader campaign that exploits npm's publishing capabilities to inflate developer reputation scores through malicious practices. The package is designed to automate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability arises from the presence of malicious code within the samehada-zs-r7 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, which can lead to a compromised npm registry and potential security risks for developers who unknowingly use these packages. The origin of this issue is linked to a token reward campaign that incentivizes such malicious behavior.

How To Fix

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

npm uninstall samehada-zs-r7

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 remove the samehada-zs-r7 package from your project by executing the following command: npm uninstall samehada-zs-r7. This will prevent any potential exploitation until a fixed version is available.

Conclusion

The samehada-zs-r7 package poses a significant risk due to its malicious code that manipulates the npm registry. It is crucial for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard your projects from potential threats.

See every vulnerability recorded for samehada-zs-r7 →

Share this vulnerability

FAQ

The samehada-zs-r7 package is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.

The malicious code can alter your package.json file, remove private flags, and publish unwanted variants, which can compromise your project's integrity and security.

If you have installed the samehada-zs-r7 package, it is recommended to uninstall it immediately and monitor your project for any unusual behavior.

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

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

How To Fix

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

npm uninstall samehada-zs-r7

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