Malicious Code Injection in divine_antelope_0xrequest Package
Summary
MAL-2025-101681: Malicious code in divine_antelope_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 divine_antelope_0xrequest package is part of the npm ecosystem, primarily used for various web development tasks. 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, making them a significant threat to developers and users alike.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the divine_antelope_0xrequest package, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive data and the compromise of application integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall divine_antelope_0xrequest
If 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, consider removing the divine_antelope_0xrequest package from your project if it is not essential. You can do this by executing the following command: npm uninstall divine_antelope_0xrequest. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The divine_antelope_0xrequest package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential to take immediate action by updating or removing the package to safeguard your application. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for divine_antelope_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.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
The risks include unauthorized access to sensitive data, application integrity compromise, and potential exposure to further malicious activities.
Check the npm registry for any updated versions of the divine_antelope_0xrequest package that address this vulnerability.
As a temporary measure, remove the package from your project and monitor your package-lock.json for unauthorized changes.