Malicious Code Detected in worried_orca_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-111010: Malicious code in worried_orca_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 package 'worried_orca_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the developers relying on it.
Vulnerability Detail
The vulnerability in 'worried_orca_z3n' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, leading to pollution of the npm registry. The malicious payload can compromise the security of applications that depend on this package, potentially allowing unauthorized access or manipulation of the software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall worried_orca_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 this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include 'worried_orca_z3n' in its dependencies. You can also use tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The 'worried_orca_z3n' package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity and security of their applications.
See every vulnerability recorded for worried_orca_z3n →
FAQ
'worried_orca_z3n' is an npm package that has been identified as containing malicious code designed to manipulate the npm registry.
The vulnerability can lead to unauthorized changes in your application's dependencies, potentially compromising its security and functionality.
You should uninstall the package immediately using 'npm uninstall worried_orca_z3n' and monitor your project for any further vulnerabilities.
Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
