Malicious Code Injection in buckley-validator-catalyst Package

buckley-validator-catalyst Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100144: Malicious code in buckley-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 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

The buckley-validator-catalyst package is part of the npm ecosystem, primarily used for validating and processing data within applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package, like others in the campaign, is designed to manipulate package metadata and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward system. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of applications relying on this package.

How To Fix

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

npm uninstall buckley-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 buckley-validator-catalyst package from your project until a secure version is released. Use the following command: npm uninstall buckley-validator-catalyst. This will prevent any malicious code from executing in your application.

Conclusion

The buckley-validator-catalyst package has been identified as containing malicious code that can compromise applications. It is crucial to update or remove the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for buckley-validator-catalyst →

Share this vulnerability

FAQ

It is an npm package used for data validation and processing, but it has been compromised by malicious code.

The malicious code can modify your package.json, remove security flags, and republish harmful variants, potentially compromising your application's integrity.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

As a workaround, consider uninstalling the package until a secure version is available to prevent any malicious activity.

Detailed information can be found in the vulnerability report and by monitoring updates from the package repository.

How To Fix

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

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