Malicious Code Injection in samehadaku-sesas-sur7 Package: npm Vulnerability Overview

samehadaku-sesas-sur7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165734: Malicious code in samehadaku-sesas-sur7 (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 samehadaku-sesas-sur7 package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a tool within this campaign, but it has been compromised to include malicious code that alters package metadata and publishes unauthorized variants.

Vulnerability Detail

The vulnerability in the samehadaku-sesas-sur7 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of derivative packages to inflate developer reputation scores. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as the degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall samehadaku-sesas-sur7

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-sesas-sur7 package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The samehadaku-sesas-sur7 package has been identified as containing malicious code that poses a significant risk to developers and the integrity of the npm ecosystem. It is essential to take immediate action to update or remove this package and to utilize tools like Vulert for ongoing monitoring of vulnerabilities in your projects.

See every vulnerability recorded for samehadaku-sesas-sur7 →

Share this vulnerability

FAQ

The samehadaku-sesas-sur7 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

The malicious code modifies your package.json file, potentially exposing your project to security risks and cluttering the npm registry with unauthorized package versions.

If you have installed the samehadaku-sesas-sur7 package, it is crucial to remove it and update your dependencies to eliminate any potential risks.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Detailed information about this vulnerability can be found in the vulnerability report provided by Amazon Inspector and on the npm registry.

How To Fix

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

npm uninstall samehadaku-sesas-sur7

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