Malicious Code Injection in future_mole_0xrequest Package
Summary
MAL-2025-102999: Malicious code in future_mole_0xrequest (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 future_mole_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automated publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability originates from the malicious payload embedded within the future_mole_0xrequest package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers and users by potentially introducing harmful code into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall future_mole_0xrequestIf 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 future_mole_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which alerts you in real-time for open-source vulnerabilities.
Conclusion
The future_mole_0xrequest package contains malicious code that poses significant risks to developers and their applications. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for future_mole_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed for automated publishing of derivative packages.
The malicious code modifies your package.json file, potentially introducing harmful changes and republishing variants that can compromise your application's integrity.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the future_mole_0xrequest package immediately using 'npm uninstall future_mole_0xrequest' and look for alternatives.
Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
