Malicious Code Injection in awful_nightingale_requirement Package
Summary
MAL-2025-93333: Malicious code in awful_nightingale_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 awful_nightingale_requirement package is part of the npm ecosystem, typically used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with random names.
Vulnerability Detail
The vulnerability in the awful_nightingale_requirement package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall awful_nightingale_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 awful_nightingale_requirement package from your project by executing: npm uninstall awful_nightingale_requirement. This will prevent any malicious code from executing in your application until a secure version is available.
Conclusion
The awful_nightingale_requirement package contains a serious vulnerability that can compromise the integrity of 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 in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for awful_nightingale_requirement →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can lead to the modification of your package.json file, potentially exposing your application to security risks and affecting its integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Regularly update your dependencies, use tools like Vulert for monitoring vulnerabilities, and review package sources before installation.
Consider removing the package from your project as a temporary measure until a secure version is released.
