Malicious Code Injection in safe_elephant_z3n Package
Summary
MAL-2025-96432: Malicious code in safe_elephant_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 safe_elephant_z3n package is part of the npm ecosystem, which is widely used for managing JavaScript packages. 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 exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the safe_elephant_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants of the package, polluting the npm registry and potentially compromising the integrity of other packages. The malicious code can lead to unauthorized access and manipulation of the developer's environment, making it critical to address this issue promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall safe_elephant_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 safe_elephant_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes and ensure that your development environment is secure.
Conclusion
The safe_elephant_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for any similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for safe_elephant_z3n →
FAQ
The safe_elephant_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json and potentially exposes your environment to further attacks.
If you have installed the safe_elephant_z3n package, you should uninstall it immediately using the command npm uninstall safe_elephant_z3n.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground.
Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.
