Malicious Code Injection in fauzankusuma Package: npm Vulnerability Overview
Summary
MAL-2025-171207: Malicious code in fauzankusuma (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 fauzankusuma package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is linked to the tea.xyz token reward scheme, which incentivizes developers to inflate their reputation scores through automated publishing of malicious variants.
Vulnerability Detail
The vulnerability in the fauzankusuma package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The malicious payload is designed to exploit the npm ecosystem, affecting developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fauzankusuma
If 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, consider removing the fauzankusuma package from your project until a secure version is available. You can do this by executing the command: 'npm uninstall fauzankusuma'. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The fauzankusuma package poses a significant risk due to its malicious code injection capabilities. Developers should take immediate action to remove or update this package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for fauzankusuma →
FAQ
The fauzankusuma package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
This vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
If you have installed fauzankusuma, it is recommended to uninstall the package immediately and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.