Malicious Code Injection in townsend-validator-catalyst: A Threat to npm Packages
Summary
MAL-2025-109786: Malicious code in townsend-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The townsend-validator-catalyst package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is intended to facilitate certain functionalities within applications that utilize the tea.xyz token reward system. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages, potentially compromising the integrity of applications that depend on it.
Vulnerability Detail
The vulnerability in the townsend-validator-catalyst package stems from its association with a malicious campaign that modifies package.json files to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, which can lead to pollution of the npm registry. This behavior not only affects the reputation of developers but also poses significant risks to applications relying on these packages, as they may inadvertently incorporate malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall townsend-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 townsend-validator-catalyst package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The townsend-validator-catalyst package poses a significant threat due to its malicious behavior, which can compromise applications relying on it. It is essential to take immediate action by removing the package and monitoring your project for vulnerabilities to ensure the security of your software.
See every vulnerability recorded for townsend-validator-catalyst →
FAQ
It is an npm package that is part of the tea.xyz token reward system, but it has been identified as malicious.
It can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the package immediately and look for alternatives or updates.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
