Malicious Code Injection in colonial_starfish_z3n Package

colonial_starfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93615: Malicious code in colonial_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 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 colonial_starfish_z3n 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. Its primary functionality revolves around enhancing developer reputation scores through the creation of numerous variants of the package, which can lead to pollution of the npm registry.

Vulnerability Detail

The vulnerability in the colonial_starfish_z3n package originates from its malicious intent to modify the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.

How To Fix

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

npm uninstall colonial_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 colonial_starfish_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your dependencies for any updates or vulnerabilities.

Conclusion

The colonial_starfish_z3n 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 your dependencies for any vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for colonial_starfish_z3n →

Share this vulnerability

FAQ

The colonial_starfish_z3n package is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project and potentially affecting other developers.

You should uninstall the colonial_starfish_z3n package immediately and check your package-lock.json for any references to it.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

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 colonial_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