Malicious Code Injection in temporary_weasel_z3n Package
Summary
MAL-2025-109537: Malicious code in temporary_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 temporary_weasel_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 automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the temporary_weasel_z3n package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to flood the npm registry with numerous variants, thereby polluting it and potentially leading to security risks for developers who may unknowingly use these compromised packages. The malicious code is part of a broader scheme to exploit the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall temporary_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 avoid using the temporary_weasel_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The temporary_weasel_z3n package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools to monitor for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for temporary_weasel_z3n →
FAQ
The temporary_weasel_z3n package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores for token rewards.
The vulnerability can lead to the injection of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the temporary_weasel_z3n package immediately and check for any dependencies that may be affected.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
