Malicious Code Injection in eastern_ox_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-94161: Malicious code in eastern_ox_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 eastern_ox_z3n is part of a broader malicious campaign targeting the npm registry, primarily associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate npm's publishing system, generating numerous derivative packages with the intent of inflating developer reputation scores. Its functionality is compromised by the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in eastern_ox_z3n stems from its inclusion in a malicious package campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The malicious payload is designed to exploit npm's publishing mechanisms, creating a significant risk for developers who inadvertently use this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eastern_ox_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, avoid using the eastern_ox_z3n package altogether. If you need similar functionality, consider looking for reputable alternatives that do not have a history of malicious behavior.
Conclusion
The eastern_ox_z3n package poses a significant risk due to its malicious nature, which exploits npm's publishing system. Developers should take immediate action to remove this package and consider using alternative solutions. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for eastern_ox_z3n →
FAQ
eastern_ox_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
You can check if your project is affected by using tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
If you have installed eastern_ox_z3n, you should uninstall it immediately using the command 'npm uninstall eastern_ox_z3n'.
Yes, look for well-reviewed and actively maintained packages that provide similar functionality without the malicious behavior.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
