Malicious Code Injection in pitts-validator-catalyst: A Threat to npm Packages

pitts-validator-catalyst Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107080: Malicious code in pitts-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 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 pitts-validator-catalyst package is part of the npm ecosystem, primarily used for validating data within applications. It is designed to facilitate the development process by providing validation tools. However, this package has been identified as part of a malicious campaign that exploits npm's package management system, leading to serious security concerns.

Vulnerability Detail

The vulnerability stems from the pitts-validator-catalyst package being associated with the tea.xyz token reward campaign, which has been flooding npm with malicious packages. These packages contain scripts that automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, ultimately polluting the npm registry and potentially compromising applications that rely on this package.

How To Fix

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

npm uninstall pitts-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 measure, you can prevent the use of the pitts-validator-catalyst package by removing it from your package.json and running the following command: npm uninstall pitts-validator-catalyst. This will help in avoiding any potential exploitation until a secure version is released.

Conclusion

The pitts-validator-catalyst package poses a significant security risk due to its association with malicious activities aimed at exploiting npm's package management system. It is essential for developers to take immediate action by removing this package and monitoring their applications for vulnerabilities.

See every vulnerability recorded for pitts-validator-catalyst →

Share this vulnerability

FAQ

It is an npm package used for data validation in applications, but it has been compromised with malicious code.

If your application uses the pitts-validator-catalyst package, it may be at risk of being exploited through malicious code that can alter your package management and inflate reputation scores.

You should uninstall the pitts-validator-catalyst package immediately to prevent any potential security risks.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall pitts-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