Malicious Code Injection in Forthcoming Wombat 0xRequest Package
Summary
MAL-2025-102877: Malicious code in forthcoming_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 forthcoming_wombat_0xrequest package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the forthcoming_wombat_0xrequest package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The ramifications include unauthorized access to sensitive data and the potential for further exploitation of the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall forthcoming_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 remove the forthcoming_wombat_0xrequest package from your project until a secure version is released. This can be done using the command: npm uninstall forthcoming_wombat_0xrequest.
Conclusion
The forthcoming_wombat_0xrequest package poses a significant security risk due to its malicious code that modifies essential project files and repopulates the npm registry with harmful variants. It is crucial to take immediate action by updating or removing the package to safeguard your application.
See every vulnerability recorded for forthcoming_wombat_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The malicious code can modify your package.json file, remove private flags, and continuously republish variants, which can lead to security vulnerabilities in your application.
You should immediately update the package to a patched version or remove it from your project until a secure version is available.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
