Malicious Code Injection in complex_constrictor_z3n: A Threat to npm Packages
Summary
MAL-2025-93679: Malicious code in complex_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 'complex_constrictor_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the creation of derivative packages.
Vulnerability Detail
The vulnerability in 'complex_constrictor_z3n' originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous packages that contain scripts designed to automatically publish variants with altered metadata. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to pollution of the npm registry and potential security risks for developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall complex_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 measure, you can avoid using the 'complex_constrictor_z3n' package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json 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 'complex_constrictor_z3n' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard your applications from such threats.
See every vulnerability recorded for complex_constrictor_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and its dependencies.
You should uninstall the 'complex_constrictor_z3n' package immediately and check for any other affected packages in your project.
Yes, regularly update your packages, use trusted sources, and employ tools like Vulert to monitor for vulnerabilities in your dependencies.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your package-lock.json without needing to sign up.
