Malicious Code Injection in witty_trout_requirement Package
Summary
MAL-2025-97396: Malicious code in witty_trout_requirement (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 witty_trout_requirement package is part of the npm ecosystem, often utilized in JavaScript projects for managing dependencies. However, it has been identified as part of a malicious campaign that aims to exploit npm's package management system. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages designed to manipulate developer reputation scores.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the witty_trout_requirement package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who inadvertently use these packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall witty_trout_requirementIf 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 witty_trout_requirement package from your project if it is not essential. Use the following command to uninstall it: npm uninstall witty_trout_requirement. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The witty_trout_requirement package poses a significant security risk due to its malicious code that alters project files and repackages itself. It is essential to take immediate action by updating or removing the package and employing monitoring tools like Vulert to safeguard your projects against future vulnerabilities.
See every vulnerability recorded for witty_trout_requirement →
FAQ
witty_trout_requirement is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
The vulnerability can lead to unauthorized modifications of your package.json file and the introduction of potentially harmful packages into your project.
You should uninstall the witty_trout_requirement package immediately and monitor your project for any unexpected changes.
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 check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, keep your packages updated, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
