Malicious Code Injection in christian_rooster-tool Package

christian_rooster-tool Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100399: Malicious code in christian_rooster-tool (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 christian_rooster-tool package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This package is designed to automatically generate and publish derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the christian_rooster-tool package originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, which can compromise the integrity of the npm registry and potentially lead to the installation of malicious code by unsuspecting developers.

How To Fix

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

npm uninstall christian_rooster-tool

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 christian_rooster-tool package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The christian_rooster-tool package has been identified as a malicious entity within the npm ecosystem, capable of compromising projects through the injection of harmful code. It is crucial for developers to remove this package and monitor their dependencies to maintain the security of their applications.

See every vulnerability recorded for christian_rooster-tool →

Share this vulnerability

FAQ

The christian_rooster-tool package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

This vulnerability can compromise the integrity of your project by introducing malicious code and polluting the npm registry with unwanted packages.

You should immediately remove the christian_rooster-tool package from your project and consider using alternative packages.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground.

Regularly update your dependencies, review their source code, and utilize tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall christian_rooster-tool

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