Malicious Code Injection in cosmiccurator: A Threat to npm Users

cosmiccurator Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171071: Malicious code in cosmiccurator (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

cosmiccurator is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate certain functionalities within the ecosystem, but it has been compromised. The vulnerability stems from malicious scripts that modify package metadata, leading to the creation of numerous derivative packages with the intent to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability in cosmiccurator originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically publish variants with altered metadata, including the removal of private flags and randomization of package names. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall cosmiccurator

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 cosmiccurator package until a secure version is released. Additionally, consider using the following command to audit your npm packages for vulnerabilities: 'npm audit'. This will help identify any other potential security issues in your project.

Conclusion

The cosmiccurator package has been identified as vulnerable due to its association with malicious scripts that compromise the npm registry. It is crucial for developers to stay informed about such vulnerabilities and take immediate action to secure their projects by updating or removing affected packages.

See every vulnerability recorded for cosmiccurator →

Share this vulnerability

FAQ

cosmiccurator is an npm package associated with the tea.xyz token reward campaign, designed to facilitate certain functionalities within its ecosystem.

The vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security, potentially allowing unauthorized access or data manipulation.

If you have installed cosmiccurator, you should immediately update the package to the latest version or remove it from your project to mitigate any risks.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

Yes, 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 cosmiccurator

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