Malicious Code Injection in Constellationseeker: A Threat to npm Packages

constellationseeker Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171065: Malicious code in constellationseeker (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Constellationseeker is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate interactions within the tea protocol ecosystem, which rewards developers with tokens for contributions. However, it has been identified as a malicious package that can compromise the integrity of the npm registry and the security of applications that depend on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the constellationseeker package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to the npm registry, leading to pollution of the registry and potential exploitation of applications that rely on this package. The origin of this vulnerability is linked to a broader campaign that aims to inflate developer reputation scores through deceptive practices.

How To Fix

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

npm uninstall constellationseeker

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 constellationseeker package altogether 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 constellationseeker package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package from their projects and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate potential threats to your applications.

See every vulnerability recorded for constellationseeker →

Share this vulnerability

FAQ

Constellationseeker is an npm package associated with the tea.xyz token reward campaign, designed to facilitate interactions within the tea protocol ecosystem.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially leading to security vulnerabilities in your application.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

You should uninstall the constellationseeker package immediately using 'npm uninstall constellationseeker' and look for alternative packages.

Currently, there is no patch available for constellationseeker. The best course of action is to remove the package and monitor for any updates.

How To Fix

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

npm uninstall constellationseeker

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