Malicious Code Injection in celestialseer Package: npm Vulnerability

celestialseer Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171013: Malicious code in celestialseer (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 celestialseer package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm environment. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the celestialseer package originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry with potentially harmful variants, posing a significant risk to users who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall celestialseer

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 celestialseer package until a secure version is released. Additionally, consider using the following command to uninstall the package: npm uninstall celestialseer to mitigate any immediate risks.

Conclusion

The celestialseer package has been identified as a vector for malicious code injection, primarily due to its involvement in a campaign that exploits npm's publishing features. It is essential for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications.

See every vulnerability recorded for celestialseer →

Share this vulnerability

FAQ

The celestialseer package is a JavaScript library available on npm, used for various functionalities within JavaScript applications.

The vulnerability can lead to the installation of malicious code that modifies your package.json file, potentially compromising your application's integrity and security.

If you have installed celestialseer, it is recommended to uninstall the package immediately and monitor for any updates or patches from the maintainers.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for 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 GitHub repository for malicious packages.

How To Fix

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

npm uninstall celestialseer

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