Malicious Code Injection in firascroissant Package: npm Vulnerability Overview
Summary
MAL-2025-171226: Malicious code in firascroissant (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 firascroissant package is part of the npm ecosystem, often utilized for various JavaScript applications. It is designed to facilitate the development and management of Node.js applications. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the firascroissant package originates from its involvement in a token reward scheme that floods the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags and altering version numbers. They generate random package names, primarily themed around Indonesian culture, and continuously republish these variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall firascroissantIf 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 firascroissant package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes or additions.
Conclusion
The firascroissant package poses a significant security risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for any vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for firascroissant →
FAQ
The firascroissant package is a JavaScript package available on npm, used for various development purposes but has been compromised with malicious code.
This vulnerability can lead to the pollution of your npm registry, potentially compromising the integrity of your application and affecting its performance.
You should uninstall the firascroissant package immediately and check for any other affected packages in your project.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
