Malicious Code Vulnerability in static_orca_z3n Package
Summary
MAL-2025-109084: Malicious code in static_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 static_orca_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been compromised to include malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the static_orca_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 to continuously republish variants, thereby polluting the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall static_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 remove the static_orca_z3n package from your project by executing: npm uninstall static_orca_z3n. This will prevent any malicious code from executing in your environment until a secure version is available.
Conclusion
The static_orca_z3n package has been identified as containing malicious code that compromises the integrity of npm projects. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for static_orca_z3n →
FAQ
The static_orca_z3n package is part of a campaign that generates derivative npm packages to inflate developer reputation scores.
The malicious code modifies your package.json file, potentially exposing your project to security risks and affecting the integrity of your npm dependencies.
You should uninstall the static_orca_z3n package immediately and check for any unauthorized changes in your project files.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, use tools like Vulert for monitoring vulnerabilities, and review package sources before installation.
