Malicious Code Vulnerability in firm_crawdad_requirement Package
Summary
MAL-2025-94521: Malicious code in firm_crawdad_requirement (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 firm_crawdad_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the development process by providing reusable code components. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability stems from the firm_crawdad_requirement package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file, removing private flags and changing version numbers. The malicious payload generates random package names and continuously republishes variants, which can lead to reputation inflation and potential security breaches for developers using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall firm_crawdad_requirementIf 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 prevent the installation of the firm_crawdad_requirement package by using the npm shrinkwrap feature or by locking your dependencies in package-lock.json. This will ensure that only the specified versions of packages are installed, avoiding the malicious package.
Conclusion
The firm_crawdad_requirement package poses a significant security risk due to its association with a malicious npm campaign. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your software.
See every vulnerability recorded for firm_crawdad_requirement →
FAQ
The firm_crawdad_requirement package is an npm package used for managing dependencies in JavaScript applications, but it has been identified as part of a malicious campaign.
This vulnerability can lead to the installation of malicious code that modifies your package.json file, potentially compromising your application's integrity and security.
If you have installed the firm_crawdad_requirement package, you should uninstall it immediately and check for any alternative packages that are secure.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
