Malicious Code Injection in renewed_mackerel_0xrequest Package
Summary
MAL-2025-107901: Malicious code in renewed_mackerel_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 renewed_mackerel_0xrequest package is part of the npm ecosystem, primarily used for managing requests in applications. It is designed to facilitate communication between services and handle data efficiently. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from the package being associated with a token reward campaign that floods npm with malicious packages. These packages contain scripts that automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry. This can lead to unauthorized access, data breaches, and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall renewed_mackerel_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, avoid using the renewed_mackerel_0xrequest package until a secure version is released. You can also monitor your package dependencies using tools like Vulert, which analyzes your package-lock.json file for vulnerabilities in real-time.
Conclusion
The renewed_mackerel_0xrequest package has been identified as a vector for malicious code injection, posing significant risks to applications that utilize it. Immediate action is required to remove the package and monitor for updates. Utilizing tools like Vulert can help maintain the security of your application by providing real-time vulnerability alerts.
See every vulnerability recorded for renewed_mackerel_0xrequest →
FAQ
It is an npm package used for managing requests in applications, but it has been compromised with malicious code.
The vulnerability can lead to unauthorized access and data breaches, compromising the integrity of your application.
Remove the package immediately and monitor for any updates or patches that may address the vulnerability.
You can use Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
