Malicious Code Injection in invisible_guppy_requirement Package
Summary
MAL-2025-95115: Malicious code in invisible_guppy_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
Background
The 'invisible_guppy_requirement' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to manipulate npm's registry. The package's primary function is to facilitate token rewards, but it has been compromised to include harmful scripts that can affect developers and their projects.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the 'invisible_guppy_requirement' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the automatic publication of derivative packages. This behavior not only pollutes the npm registry but also poses a risk to developers by inflating reputation scores fraudulently. The malicious payload is designed to continuously republish variants, making it difficult to track and mitigate the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall invisible_guppy_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 'invisible_guppy_requirement' package from your project by executing the following command: 'npm uninstall invisible_guppy_requirement'. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The 'invisible_guppy_requirement' package has been identified as containing malicious code that can compromise your project. It is crucial to take immediate action by updating or removing the package to safeguard your application. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
See every vulnerability recorded for invisible_guppy_requirement →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious code.
The malicious code modifies your package.json, removes private flags, and publishes derivative packages, which can lead to reputation inflation and registry pollution.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If an update is not available, consider removing the package as a temporary measure and monitor for any updates from the maintainers.
Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
