Malicious Code Injection in samehadaku-tus-ur7: A Threat to npm Packages

samehadaku-tus-ur7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165741: Malicious code in samehadaku-tus-ur7 (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 package 'samehadaku-tus-ur7' is part of a larger ecosystem within npm, often associated with token reward campaigns. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to developers and their applications.

Vulnerability Detail

The vulnerability in 'samehadaku-tus-ur7' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants. This can result in the pollution of the npm registry and potential exploitation of developers who unknowingly integrate these packages into their projects.

How To Fix

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

npm uninstall samehadaku-tus-ur7

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, consider removing the 'samehadaku-tus-ur7' package from your project until a secure version is released. You can do this by running the following command: npm uninstall samehadaku-tus-ur7.

Conclusion

The 'samehadaku-tus-ur7' package poses a significant security threat due to its malicious code that modifies essential files and repackages itself. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications.

See every vulnerability recorded for samehadaku-tus-ur7 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and repackages the software, leading to potential security risks.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Using this package may lead to security breaches, reputation damage, and the risk of integrating malicious code into your application.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

Consider removing the package from your project as a temporary measure until a secure version is available.

How To Fix

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

npm uninstall samehadaku-tus-ur7

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