Malicious Code Injection in tight_aphid_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-109696: Malicious code in tight_aphid_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
tight_aphid_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm registry and poses risks to developers relying on it.
Vulnerability Detail
The vulnerability in tight_aphid_z3n stems from its inclusion in a series of malicious packages designed to manipulate the npm registry. The package contains scripts that automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other packages and developers who may unknowingly depend on these malicious variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tight_aphid_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 tight_aphid_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The tight_aphid_z3n package poses a significant risk to the npm ecosystem due to its malicious behavior aimed at manipulating the npm registry. Developers are advised to remove this package from their projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for tight_aphid_z3n →
FAQ
tight_aphid_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially affecting other packages and developers who may unknowingly depend on the malicious variants generated by tight_aphid_z3n.
It is recommended to remove the tight_aphid_z3n package from your project immediately and monitor for any updates or patches that may be released.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
