Malicious Code Injection in sexual_mackerel_0xrequest Package
Summary
MAL-2025-108581: Malicious code in sexual_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 sexual_mackerel_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the sexual_mackerel_0xrequest package being linked to a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names, leading to pollution of the npm registry. The malicious payload can compromise the security of applications relying on this package, potentially leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sexual_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 workaround, you can avoid using the sexual_mackerel_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies to ensure they are secure.
Conclusion
The sexual_mackerel_0xrequest package has been identified as a vector for malicious code injection, posing significant risks to developers and the integrity of the npm ecosystem. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain application security.
See every vulnerability recorded for sexual_mackerel_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security.
You should remove the sexual_mackerel_0xrequest package from your project and look for alternatives.
Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
