Malicious Code Injection in regular_alligator_z3n: A Threat to npm Packages
Summary
MAL-2025-96246: Malicious code in regular_alligator_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'regular_alligator_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in 'regular_alligator_z3n' originates from malicious code embedded in the package, which 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, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers by inflating reputation scores fraudulently and may lead to security risks if other packages depend on these compromised versions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall regular_alligator_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 remove the 'regular_alligator_z3n' package from your project by executing the command: 'npm uninstall regular_alligator_z3n'. This will prevent any malicious code from executing until a patched version is available.
Conclusion
The 'regular_alligator_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for regular_alligator_z3n →
FAQ
The malicious code modifies package.json to remove private flags and generates random package names, leading to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Compromised packages can lead to security vulnerabilities, data breaches, and the potential for malicious actors to exploit your application.
Yes, tools like Vulert can automatically monitor your package-lock.json file for vulnerabilities and alert you in real-time.
If you cannot update the package, consider removing it from your project as a temporary measure to mitigate risks.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
