Malicious Code Injection in arifcroissant Package: npm Vulnerability
Summary
MAL-2025-170908: Malicious code in arifcroissant (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 arifcroissant package is part of the npm ecosystem, primarily used for various JavaScript applications. It is one of the many packages that emerged during the tea.xyz token reward campaign, which aimed to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package, like others in the campaign, is designed to manipulate the npm registry by creating numerous variants of itself with altered names and metadata.
Vulnerability Detail
The vulnerability in the arifcroissant package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potentially compromising the integrity of applications that depend on this package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been identified as a source of numerous malicious packages flooding the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall arifcroissantIf 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 arifcroissant 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 unauthorized changes.
Conclusion
The arifcroissant package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with variants. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities to maintain application integrity.
See every vulnerability recorded for arifcroissant →
FAQ
The arifcroissant package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security by introducing malicious code.
You should uninstall the arifcroissant package immediately using the command npm uninstall arifcroissant and check for any unauthorized changes in your project.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies using tools like npm audit, keep your packages updated, and monitor your project with services like Vulert to catch vulnerabilities early.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
