Malicious Code Injection in xeric_ox_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-97453: Malicious code in xeric_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 'xeric_ox_z3n' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate developer reputation scores by flooding the npm registry with derivative packages that have randomized names. It is crucial for developers to understand the implications of using such packages, as they can lead to significant security risks and pollution of the package registry.
Vulnerability Detail
The vulnerability in 'xeric_ox_z3n' stems from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to applications relying on these packages, potentially leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xeric_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 temporary measure, you can avoid using the 'xeric_ox_z3n' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'xeric_ox_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers must take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can enhance security and provide peace of mind.
See every vulnerability recorded for xeric_ox_z3n →
FAQ
The primary threat is the malicious code that modifies package.json files and floods the npm registry with harmful variants, potentially compromising application security.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
Immediately remove the package from your project and check for any unauthorized changes in your package.json file. Consider updating to a secure version if available.
Yes, look for reputable packages that offer similar functionalities without the associated risks. Always verify the package's credibility before installation.
Vulert uses your package-lock.json to monitor and alert you in real-time about open-source vulnerabilities, helping you maintain a secure application.
