Malicious Code Injection in amie-validator-catalyst: A Threat to npm Packages
Summary
MAL-2025-99399: Malicious code in amie-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 amie-validator-catalyst package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is designed to validate certain functionalities within applications. However, it has been compromised, making it susceptible to malicious code that can affect the integrity of the npm registry and the applications relying on it.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the amie-validator-catalyst package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores through the tea.xyz token reward campaign, which leads to the continuous republishing of these compromised packages, polluting the npm registry and potentially exposing applications to further risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall amie-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 remove the amie-validator-catalyst package from your project by executing: 'npm uninstall amie-validator-catalyst'. This will prevent the malicious code from executing until a secure version is available.
Conclusion
The amie-validator-catalyst package has been compromised with malicious code that poses a significant risk to applications using it. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for amie-validator-catalyst →
FAQ
The malicious code can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to avoid exposure to the vulnerability.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security updates for the packages you use.
Detailed information about this vulnerability can be found in the Open Source Vulnerability database and through security advisories related to npm packages.
