Malicious Code Injection in remarkable_starfish_z3n Package

remarkable_starfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96290: Malicious code in remarkable_starfish_z3n (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The remarkable_starfish_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. It is designed to facilitate various functionalities within applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation and publication of numerous derivative packages. This vulnerability poses significant risks to developers and users alike, as it can lead to the proliferation of harmful code within the npm registry.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. These packages contain scripts that automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can compromise the integrity of the npm ecosystem and potentially introduce security risks to 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 remarkable_starfish_z3n

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 workaround, you can temporarily avoid using the remarkable_starfish_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The remarkable_starfish_z3n package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial for developers to be vigilant and remove this package from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for remarkable_starfish_z3n →

Share this vulnerability

FAQ

It is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the introduction of malicious code, compromising the security and integrity of your application.

You should uninstall the remarkable_starfish_z3n package immediately and check for alternative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall remarkable_starfish_z3n

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