Malicious Code Injection in bewildered_constrictor_z3n Package
Summary
MAL-2025-93373: Malicious code in bewildered_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 'bewildered_constrictor_z3n' package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the generation and publication of derivative packages, which can inflate developer reputation scores. However, this package has been identified as containing malicious code that compromises its integrity and the security of applications relying on it.
Vulnerability Detail
The vulnerability in 'bewildered_constrictor_z3n' originates from its involvement in a campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the pollution of the npm registry and can potentially harm developers' reputations and the security of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bewildered_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 'bewildered_constrictor_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The 'bewildered_constrictor_z3n' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain application security.
See every vulnerability recorded for bewildered_constrictor_z3n →
FAQ
It is an npm package associated with token reward campaigns that generate derivative packages.
The malicious code can modify your package.json, remove private flags, and pollute the npm registry, potentially compromising your application's security.
You should remove the 'bewildered_constrictor_z3n' package from your project immediately and monitor for any updates or patches.
You can use Vulert, which monitors your package-lock.json for vulnerabilities and alerts you in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
