Malicious Code Injection in literary_quelea_0xrequest Package
Summary
MAL-2025-105260: Malicious code in literary_quelea_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 literary_quelea_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It 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 package, like others in the campaign, is designed to manipulate the npm registry by creating numerous variants with randomized names.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the literary_quelea_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The result is a polluted npm registry, which can compromise the integrity of the ecosystem and affect developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall literary_quelea_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 literary_quelea_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any changes that might indicate the presence of malicious packages.
Conclusion
The literary_quelea_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor for any similar vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for literary_quelea_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and its dependencies.
You should uninstall the package immediately and monitor your project for any further issues.
Yes, tools like Vulert can help monitor your project for open-source vulnerabilities using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
