Malicious Code Injection in samehada-usr7 Package

samehada-usr7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165718: Malicious code in samehada-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 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-usr7 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to inflate developer reputation scores. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior.

Vulnerability Detail

The vulnerability in the samehada-usr7 package stems from its inclusion in a campaign that deploys malicious code to manipulate package metadata. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The malicious payload can potentially harm developers by affecting their reputation and introducing security risks in applications that depend on this package.

How To Fix

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

npm uninstall samehada-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 samehada-usr7 package and any other packages associated with the tea.xyz campaign. Regularly audit your dependencies to ensure no malicious packages are included. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The samehada-usr7 package poses a significant risk due to its malicious code that alters package metadata and can lead to security vulnerabilities in applications. It is crucial to remove this package and monitor your dependencies for any potential threats.

See every vulnerability recorded for samehada-usr7 →

Share this vulnerability

FAQ

The samehada-usr7 package is an npm package linked to a token reward campaign that has been identified as malicious due to its scripts that manipulate package metadata.

This vulnerability can lead to the introduction of malicious code into your application, potentially compromising security and affecting the reputation of the developers involved.

You should remove the samehada-usr7 package from your project and monitor for any updates or patches that may address the vulnerability.

You can use tools like Vulert, which allows you to monitor your package-lock.json for open-source 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-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