Malicious Code Injection in clinical_aardwolf-biggestdev Package
Summary
MAL-2025-100598: Malicious code in clinical_aardwolf-biggestdev (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 clinical_aardwolf-biggestdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to the proliferation of harmful packages.
Vulnerability Detail
The vulnerability stems from the package being associated with a token reward campaign that floods the npm registry with malicious packages. It contains scripts designed to modify package.json files, removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially affecting other developers and users relying on npm for secure package management.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall clinical_aardwolf-biggestdevIf 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 measure, you can avoid using the clinical_aardwolf-biggestdev package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity of packages before installation.
Conclusion
The clinical_aardwolf-biggestdev package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security and integrity of their applications.
See every vulnerability recorded for clinical_aardwolf-biggestdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of harmful packages.
If your application uses this package, it may be compromised by malicious code that alters your package.json and affects your project's integrity.
You should uninstall the clinical_aardwolf-biggestdev package immediately and check your project for any unauthorized changes.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
