Malicious Code Injection in special_urial_z3n Package: npm Vulnerability Overview
Summary
MAL-2025-96702: Malicious code in special_urial_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 special_urial_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 automated scripts. It is designed to create and publish numerous derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the special_urial_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can clutter the npm registry, making it difficult for developers to find legitimate packages. The ramifications include potential security risks, as developers may unknowingly install compromised packages, leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall special_urial_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 workaround, you can manually check your package-lock.json file for any references to special_urial_z3n and remove it. You can do this by running the following command: npm uninstall special_urial_z3n. This will ensure that the malicious package is no longer part of your project dependencies.
Conclusion
The special_urial_z3n package poses a significant risk due to its malicious code that alters project files and repopulates the npm registry with compromised packages. Developers are advised to remove this package and monitor their projects for vulnerabilities to ensure security.
See every vulnerability recorded for special_urial_z3n →
FAQ
The special_urial_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to security risks and clutter in the npm registry.
You should uninstall the special_urial_z3n package immediately to mitigate any potential risks associated with its malicious code.
Currently, there is no patched version available for the special_urial_z3n package, so the best course of action is to remove it from your project.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.
