Malicious Code Injection in Respective Wombat 0xRequest Package
Summary
MAL-2025-107967: Malicious code in respective_wombat_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
Background
The 'respective_wombat_0xrequest' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions with the tea protocol, but it has been compromised to include malicious scripts that manipulate its functionality. The package is intended for developers looking to integrate with the tea protocol, but its integrity has been severely compromised due to the malicious code embedded within.
Vulnerability Detail
The vulnerability stems from malicious code embedded in the 'respective_wombat_0xrequest' package, which is part of a broader scheme to inflate developer reputation scores through the automatic generation and publication of derivative packages. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The ramifications include potential security risks for developers using this package, as it may lead to unauthorized access or manipulation of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall respective_wombat_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 workaround, avoid using the 'respective_wombat_0xrequest' package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'respective_wombat_0xrequest' package has been compromised with malicious code that poses significant risks to developers and their applications. Immediate action is required to uninstall the package and monitor for updates. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for respective_wombat_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed for developers to interact with the tea protocol.
The malicious code can modify your package.json file, remove private flags, and publish unauthorized versions of your package, potentially compromising your application's security.
You should uninstall the package immediately using 'npm uninstall respective_wombat_0xrequest' and monitor for any updates or patches.
Yes, consider looking for other npm packages that offer similar functionality without the associated risks of malicious code.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without any signup.
