Malicious Code Injection in traditional_ox_z3n Package
Summary
MAL-2025-109804: Malicious code in traditional_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 traditional_ox_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package is particularly vulnerable due to its inclusion in a series of malicious packages that aim to inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in the traditional_ox_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for fraudulent purposes. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the integrity of the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall traditional_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 workaround, avoid using the traditional_ox_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The traditional_ox_z3n package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for traditional_ox_z3n →
FAQ
The traditional_ox_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and affecting the integrity of your application.
If you have installed the traditional_ox_z3n package, you should uninstall it immediately using 'npm uninstall traditional_ox_z3n' and check for any other affected packages.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
