Malicious Code Injection in yappy_goose_requirement Package
Summary
MAL-2025-97475: Malicious code in yappy_goose_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 yappy_goose_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the automatic generation of derivative packages.
Vulnerability Detail
The vulnerability in the yappy_goose_requirement package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. This allows the package to generate random names for derivative packages, which are then republished to the npm registry, polluting it with potentially harmful code. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall yappy_goose_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 measure, you can avoid using the yappy_goose_requirement package until a patched version is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.
Conclusion
The yappy_goose_requirement package poses a significant security risk due to its malicious code injection vulnerability. It is essential for developers to remain vigilant, update their dependencies, and utilize monitoring tools like Vulert to safeguard their applications against such threats.
See every vulnerability recorded for yappy_goose_requirement →
FAQ
It is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should update the package to the latest version or remove it from your project until a fix is available.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
