Malicious Code Injection in orthodox_weasel_z3n: A Threat to npm Packages
Summary
MAL-2025-95796: Malicious code in orthodox_weasel_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 'orthodox_weasel_z3n' is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.
Vulnerability Detail
The vulnerability in 'orthodox_weasel_z3n' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. The ramifications of this vulnerability include potential loss of control over package integrity, reputational damage for developers, and increased difficulty in managing dependencies due to the proliferation of malicious variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall orthodox_weasel_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 'orthodox_weasel_z3n' package from your project by executing: 'npm uninstall orthodox_weasel_z3n'. This will help mitigate the risk until a secure version is available.
Conclusion
The 'orthodox_weasel_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial for developers to take immediate action by updating or removing the package to protect their applications.
See every vulnerability recorded for orthodox_weasel_z3n →
FAQ
The vulnerability involves malicious code that alters package metadata and publishes derivative packages to the npm registry.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to compromised package integrity, reputational damage, and challenges in managing dependencies due to the proliferation of malicious variants.
Check the npm registry for a patched version of 'orthodox_weasel_z3n' and update your package accordingly.
As a temporary measure, consider uninstalling the package to mitigate risks until a secure version is available.
