Malicious Code Injection in ugliest_constrictor_z3n: A Threat to npm Packages
Summary
MAL-2025-97069: Malicious code in ugliest_constrictor_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 'ugliest_constrictor_z3n' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the security of applications that depend on these packages.
Vulnerability Detail
The vulnerability in 'ugliest_constrictor_z3n' originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications using these packages. The malicious payload is part of a broader campaign that exploits npm's ecosystem for token rewards, making it a significant concern for developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ugliest_constrictor_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 avoid using the 'ugliest_constrictor_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.
Conclusion
The 'ugliest_constrictor_z3n' package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for ugliest_constrictor_z3n →
FAQ
The main risk is that it contains malicious code that can compromise the integrity of your application by modifying package configurations and flooding the npm registry with unwanted packages.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall ugliest_constrictor_z3n' and audit your project for any other potentially affected packages.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.
Look for alternative packages that offer similar functionality without the associated risks, and ensure to review their security history before integrating them into your project.
