Malicious Code Injection in samehadakudsfds-usr7 Package

samehadakudsfds-usr7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165745: Malicious code in samehadakudsfds-usr7 (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 samehadakudsfds-usr7 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package metadata and floods the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability stems from malicious code embedded in the samehadakudsfds-usr7 package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The primary risk includes the pollution of the npm registry with numerous derivative packages, which can lead to confusion, reputation damage for developers, and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall samehadakudsfds-usr7

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 samehadakudsfds-usr7 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall samehadakudsfds-usr7.

Conclusion

The samehadakudsfds-usr7 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor for updates. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for samehadakudsfds-usr7 →

Share this vulnerability

FAQ

The samehadakudsfds-usr7 package is an npm package associated with a token reward campaign that has been identified to contain malicious code.

The malicious code modifies package metadata and floods the npm registry, which can lead to confusion and potential security risks for applications that depend on these packages.

You should uninstall the samehadakudsfds-usr7 package immediately and monitor for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security advisories for the packages you use.

How To Fix

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

npm uninstall samehadakudsfds-usr7

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