Malicious Code Injection in genuine_wren_orange-11 Package
Summary
MAL-2025-103106: Malicious code in genuine_wren_orange-11 (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 genuine_wren_orange-11 package is part of the npm ecosystem, typically used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, contains scripts designed to automatically publish derivative packages, leading to potential misuse and pollution of the npm registry.
Vulnerability Detail
The vulnerability in genuine_wren_orange-11 stems from malicious code embedded within the package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the automatic republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to inflate reputation scores. The ramifications include the potential for developers to unknowingly use compromised packages, leading to security risks and degraded trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall genuine_wren_orange-11If 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 genuine_wren_orange-11 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your dependencies.
Conclusion
The genuine_wren_orange-11 package contains malicious code that poses significant risks to applications using it. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for genuine_wren_orange-11 →
FAQ
genuine_wren_orange-11 is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through automated publishing.
The malicious code modifies your package.json file, potentially leading to the republishing of compromised packages and exposing your application to security risks.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed the genuine_wren_orange-11 package, you should remove it immediately and check for any alternative packages that do not carry the same risks.
Yes, tools like npm audit can help you identify vulnerabilities in your dependencies, and Vulert can monitor your applications for open-source vulnerabilities in real-time.
