Malicious Code Injection in nice_angelfish_z3n: A Threat to npm Packages
Summary
MAL-2025-95644: Malicious code in nice_angelfish_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 package 'nice_angelfish_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in 'nice_angelfish_z3n' originates from its association with malicious autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes developers to potential security risks and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nice_angelfish_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 measure, you can avoid using the 'nice_angelfish_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'nice_angelfish_z3n' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is essential to remove this package and monitor your dependencies for security. Utilizing tools like Vulert can help maintain the integrity of your software by providing real-time alerts for vulnerabilities.
See every vulnerability recorded for nice_angelfish_z3n →
FAQ
The package contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Remove the package immediately and check for any unauthorized changes in your project files.
Yes, consider exploring other npm packages that provide similar functionalities without the associated risks.
Vulert uses your package-lock.json to monitor and alert you in real-time for any open-source vulnerabilities in your software.
