Malicious Code Injection in helpless_nightingale_z3n Package
Summary
MAL-2025-94812: Malicious code in helpless_nightingale_z3n (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 helpless_nightingale_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity.
Vulnerability Detail
The vulnerability in the helpless_nightingale_z3n package originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in significant ramifications, including the potential for malicious actors to exploit the package for nefarious purposes, thereby affecting users who rely on this package for their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall helpless_nightingale_z3nIf 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 helpless_nightingale_z3n package from your project by executing the following command: npm uninstall helpless_nightingale_z3n. This will prevent any potential exploitation while you seek a secure alternative.
Conclusion
The helpless_nightingale_z3n package has been identified as containing malicious code that poses significant risks to users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can enhance your security posture by providing real-time monitoring for vulnerabilities.
See every vulnerability recorded for helpless_nightingale_z3n →
FAQ
The primary issue is the presence of malicious code that modifies package.json and repurposes the package for harmful activities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Using the compromised package can lead to security breaches, unauthorized access, and pollution of the npm registry, which can affect other developers.
Regularly updating packages, using tools like Vulert for monitoring vulnerabilities, and conducting security audits can help prevent similar issues.
If an immediate update is not possible, consider removing the package and looking for alternative solutions until a secure version is available.
