Malicious Code Vulnerability in secure_constrictor_z3n: npm Package Exploitation
Summary
MAL-2025-96488: Malicious code in secure_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 secure_constrictor_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that 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 a risk to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can potentially compromise the security of applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall secure_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 secure_constrictor_z3n package and replace it with a trusted alternative. Always verify the integrity of packages before including them in your project.
Conclusion
The secure_constrictor_z3n package poses a significant risk due to its malicious nature, which can compromise the security of applications relying on npm packages. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for secure_constrictor_z3n →
FAQ
secure_constrictor_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the security and integrity of applications that depend on affected packages.
You should uninstall the secure_constrictor_z3n package immediately and check for any other affected packages in your project.
Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. It requires only the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
