Malicious Code Injection in browning-validator-catalyst Package
Summary
MAL-2025-100138: Malicious code in browning-validator-catalyst (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The browning-validator-catalyst package is part of the npm ecosystem, typically used for validation tasks in JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate its own metadata and publish variants to inflate developer reputation scores, posing a significant risk to developers and their applications.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign linked to the tea.xyz token reward initiative. It contains scripts that automatically modify the package.json file, removing private flags and altering version numbers. The package generates random names and continuously republishes variants, leading to pollution of the npm registry. This behavior can compromise the integrity of applications relying on this package, potentially introducing security risks and instability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall browning-validator-catalystIf 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 browning-validator-catalyst package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The browning-validator-catalyst package has been identified as containing malicious code that can compromise applications using it. It is crucial to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your software.
See every vulnerability recorded for browning-validator-catalyst →
FAQ
It is an npm package used for validation tasks in JavaScript applications, but it has been compromised with malicious code.
The malicious code modifies your package metadata and can lead to the pollution of the npm registry, potentially compromising your application's integrity.
You should remove the browning-validator-catalyst package from your project and look for alternatives.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
