Malicious Code Injection in bakricroissant: npm Package Vulnerability
Summary
MAL-2025-170948: Malicious code in bakricroissant (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 'bakricroissant' package is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the 'bakricroissant' package stems from its inclusion in a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The malicious payload can significantly impact developers by compromising their package integrity and reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bakricroissantIf 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 'bakricroissant' package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'bakricroissant' package has been identified as a malicious npm package that modifies package metadata for harmful purposes. It is crucial to remove this package from your projects and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for bakricroissant →
FAQ
The 'bakricroissant' package is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata for token rewards.
This vulnerability can compromise the integrity of your project by introducing malicious code that alters package metadata and can lead to reputation damage in the npm registry.
If you have installed 'bakricroissant', you should uninstall it immediately using 'npm uninstall bakricroissant' and check for any dependencies that may be affected.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation. You can also check your application using the Vulert playground.
You can check if your application is affected by this vulnerability by using the Vulert playground at Vulert Scanner, where you can analyze your package-lock.json without signing up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
