Malicious Code Injection in static_wombat_0xrequest Package
Summary
MAL-2025-109086: Malicious code in static_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 static_wombat_0xrequest package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns. These packages are designed to automate the generation and publication of derivative packages, which can lead to inflated developer reputation scores. The package's functionality is compromised due to malicious scripts that alter its metadata and behavior.
Vulnerability Detail
The vulnerability in the static_wombat_0xrequest package stems from its association with the tea.xyz token reward campaign, which has been linked to the distribution of malicious code. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload can result in unauthorized access to sensitive information and the proliferation of untrustworthy packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall static_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, you can prevent the installation of the static_wombat_0xrequest package by using the following command: npm uninstall static_wombat_0xrequest. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The static_wombat_0xrequest package has been identified as containing malicious code that can compromise your application's integrity. It is crucial to take immediate action by updating or removing the package and monitoring your project for any unauthorized changes.
See every vulnerability recorded for static_wombat_0xrequest →
FAQ
It is an npm package associated with token reward campaigns that automates the generation of derivative packages.
The vulnerability can lead to unauthorized modifications of your package metadata and the introduction of untrustworthy packages into your project.
You should immediately update or uninstall the package to mitigate the risk of exploitation.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.
