Malicious Code Injection in atomic_mongoose_0xrequest Package
Summary
MAL-2025-99651: Malicious code in atomic_mongoose_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 atomic_mongoose_0xrequest package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate its own metadata and publish variants to inflate developer reputation scores, posing a significant risk to users and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the atomic_mongoose_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The malicious payload is part of a broader scheme associated with the tea.xyz token reward campaign, which aims to exploit npm for fraudulent gains. Users of this package may unknowingly contribute to the proliferation of these harmful variants, compromising their applications and potentially exposing sensitive data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall atomic_mongoose_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 atomic_mongoose_0xrequest package until a secure version is released. Additionally, you may want to implement stricter package validation and monitoring in your development environment to prevent the installation of malicious packages.
Conclusion
The atomic_mongoose_0xrequest package poses a significant risk due to its malicious code that modifies package metadata and publishes harmful variants. It is crucial for developers to take immediate action to update or remove this package to protect their applications and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for atomic_mongoose_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
The vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and expose sensitive data.
You should immediately update the package to a patched version or remove it from your project to mitigate risks.
You can use tools like 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.
