Malicious Code Injection in Stewart Validator Catalyst: npm Package Vulnerability
Summary
MAL-2025-109121: Malicious code in stewart-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
Stewart Validator Catalyst is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate certain functionalities within the ecosystem, but it has been compromised, leading to significant security concerns. The package is known for its ability to generate and publish derivative packages, which can inflate developer reputation scores for token rewards. However, this functionality has been exploited to introduce malicious code.
Vulnerability Detail
The vulnerability stems from the package being part of a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially affecting other developers and their projects. The malicious payload can lead to unauthorized access and manipulation of the package, posing a risk to users who rely on it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall stewart-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, consider removing the affected package from your project until a secure version is available. You can uninstall the package using the following command: npm uninstall stewart-validator-catalyst.
Conclusion
The stewart-validator-catalyst package has been compromised with malicious code that poses significant security risks. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Regular monitoring for vulnerabilities is essential to maintain the integrity of your software.
See every vulnerability recorded for stewart-validator-catalyst →
FAQ
The vulnerability involves malicious code that modifies package.json and floods the npm registry with derivative packages, compromising the integrity of the package.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
You should update the package to the latest patched version using the command npm update stewart-validator-catalyst or uninstall it until a secure version is available.
Failing to address this vulnerability can lead to unauthorized access, manipulation of your project, and potential damage to your reputation as a developer.
You can visit Vulert at https://vulert.com, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json.
