Malicious Code Injection in middle_starfish-notthedev Package

middle_starfish-notthedev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105827: Malicious code in middle_starfish-notthedev (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 middle_starfish-notthedev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm registry but has been compromised to include malicious scripts that manipulate package metadata. The vulnerability stems from its involvement in a scheme that generates and publishes derivative packages to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the middle_starfish-notthedev package originates from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm registry.

How To Fix

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

npm uninstall middle_starfish-notthedev

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 middle_starfish-notthedev package from your project by executing the following command: npm uninstall middle_starfish-notthedev. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The middle_starfish-notthedev package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects from potential vulnerabilities.

See every vulnerability recorded for middle_starfish-notthedev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to facilitate various functionalities but has been compromised.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry.

You should uninstall the package immediately and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Using compromised packages can lead to security breaches, loss of data integrity, and a decline in trust within the developer community.

How To Fix

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

npm uninstall middle_starfish-notthedev

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