Malicious Code Injection in visible_crocodile_z3n Package
Summary
MAL-2025-91968: Malicious code in visible_crocodile_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 visible_crocodile_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package is implicated in a malicious campaign associated with the tea.xyz token reward initiative. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the campaign. The package's functionality is compromised due to its malicious intent, making it a significant risk for developers and users alike.
Vulnerability Detail
The vulnerability originates from the visible_crocodile_z3n package, which contains malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for applications using these packages, and a compromised developer reputation system. The malicious payload is designed to exploit the npm ecosystem by flooding it with unwanted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall visible_crocodile_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 prevent the installation of the visible_crocodile_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the automatic installation of this malicious package until a permanent fix is implemented.
Conclusion
The visible_crocodile_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 from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for visible_crocodile_z3n →
FAQ
The visible_crocodile_z3n package is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.
The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, potentially compromising your project's security.
You should uninstall the visible_crocodile_z3n package immediately using the command 'npm uninstall visible_crocodile_z3n' and check for any other affected packages.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
