Malicious Code Injection in crosby-validator-catalyst Package

crosby-validator-catalyst Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101094: Malicious code in crosby-validator-catalyst (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

The crosby-validator-catalyst package is part of the npm ecosystem, primarily used for validating data in various applications. It is designed to enhance the functionality of JavaScript applications by providing validation mechanisms. However, this package has been compromised, making it susceptible to malicious activities that can affect the integrity of applications relying on it.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the crosby-validator-catalyst package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names to inflate developer reputation scores for token rewards. The malicious scripts are designed to continuously republish variants, polluting the npm registry and potentially leading to security breaches in applications that utilize this package.

How To Fix

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

npm uninstall crosby-validator-catalyst

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 remove the crosby-validator-catalyst package from your project if it is not essential. Use the following command to uninstall it: npm uninstall crosby-validator-catalyst. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The crosby-validator-catalyst package has been identified as containing malicious code that can compromise applications relying on it. It is essential to update or remove the package to mitigate risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for crosby-validator-catalyst →

Share this vulnerability

FAQ

The crosby-validator-catalyst package is used for data validation in JavaScript applications, enhancing their functionality.

The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising its security and integrity.

Yes, you can use Vulert to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert provides real-time alerts for open-source vulnerabilities.

If an immediate update is not possible, consider removing the package as a temporary measure and monitor your application closely for any unusual behavior.

Detailed information can be found in the vulnerability report provided by Amazon Inspector, which outlines the nature of the malicious code and its implications.

How To Fix

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

npm uninstall crosby-validator-catalyst

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