Malicious Code Injection in bernadine-validator-catalyst: A Threat to npm Users

bernadine-validator-catalyst Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99943: Malicious code in bernadine-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 bernadine-validator-catalyst package is part of the npm ecosystem, primarily used for validating transactions in decentralized 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 developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs malicious scripts to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This can result in developers unknowingly using compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall bernadine-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 bernadine-validator-catalyst package from your project by executing the command: 'npm uninstall bernadine-validator-catalyst'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The bernadine-validator-catalyst package has been identified as part of a malicious campaign that poses significant risks to developers using npm. It is essential to take immediate action by updating or removing the package to safeguard your applications from potential threats.

See every vulnerability recorded for bernadine-validator-catalyst →

Share this vulnerability

FAQ

It is an npm package used for validating transactions in decentralized applications, but it has been compromised by malicious actors.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Using the compromised package can lead to security vulnerabilities in your application, including unauthorized access and data breaches.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

Immediately uninstall the package and check your application for any signs of compromise. Update to a secure version if available.

How To Fix

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

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