Malicious Code Injection in alone_wren_requirement Package
Summary
MAL-2025-93202: Malicious code in alone_wren_requirement (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The 'alone_wren_requirement' package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It has been identified as part of a larger malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. This package, like others in the campaign, is designed to manipulate package metadata and publish variants to the npm registry, leading to potential security risks for developers who unknowingly use it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the 'alone_wren_requirement' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. The origin of this vulnerability is linked to a campaign that aims to exploit npm's publishing system, potentially leading to reputation damage for developers and pollution of the npm ecosystem with untrustworthy packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alone_wren_requirementIf 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 'alone_wren_requirement' 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 'alone_wren_requirement' package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with untrustworthy variants. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for alone_wren_requirement →
FAQ
The 'alone_wren_requirement' package is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata and inflating developer reputation scores.
This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
If you have installed the 'alone_wren_requirement' package, it is recommended to remove it immediately and check for any alternative packages.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
To prevent similar vulnerabilities, regularly audit your dependencies using tools like npm audit and stay updated on security advisories related to the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
