Malicious Code Injection in donkey_apricot-44: A Threat to npm Packages
Summary
MAL-2025-97712: Malicious code in donkey_apricot-44 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package donkey_apricot-44 is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with random names, thereby inflating developer reputation scores in exchange for token rewards. The malicious behavior of this package poses a significant risk to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in donkey_apricot-44 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of projects that depend on these packages. The origin of this vulnerability is linked to a token reward campaign that has flooded the npm ecosystem with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall donkey_apricot-44If 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 donkey_apricot-44 package altogether and look for alternative packages that provide similar functionality without the associated risks. Always ensure to review the package's reputation and its dependencies before installation.
Conclusion
The discovery of malicious code in donkey_apricot-44 highlights the importance of vigilance when managing npm packages. Developers should take immediate action to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for donkey_apricot-44 →
FAQ
donkey_apricot-44 is an npm package that has been identified as malicious, designed to exploit the npm publishing system.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities in your project.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using the command npm uninstall donkey_apricot-44 and look for secure alternatives.
Yes, this package is part of a broader campaign that includes several other malicious packages. It is advisable to review your dependencies regularly.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
