Malicious Code Injection in remote_yak_z3n Package - npm Vulnerability
Summary
MAL-2025-98908: Malicious code in remote_yak_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 remote_yak_z3n package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and security of the npm ecosystem.
Vulnerability Detail
The vulnerability in the remote_yak_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, often aimed at exploiting developer incentives.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall remote_yak_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 remote_yak_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall remote_yak_z3n.
Conclusion
The remote_yak_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 monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help in identifying and mitigating such risks effectively.
See every vulnerability recorded for remote_yak_z3n →
FAQ
The primary issue is that it contains malicious code that modifies package.json files and republish variants to pollute the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using the command: npm uninstall remote_yak_z3n.
Yes, you should look for alternative packages that provide similar functionality but do not have the same security risks.
Using this package can lead to security vulnerabilities in your application, including unauthorized modifications to your package.json file and exposure to malicious code.
