Malicious Code Injection in faridfromage Package: A Threat to npm Users
Summary
MAL-2025-171204: Malicious code in faridfromage (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 faridfromage package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to facilitate the development process by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by publishing numerous derivative packages with harmful scripts.
Vulnerability Detail
The vulnerability in the faridfromage package originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting developers' reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall faridfromageIf 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 measure, avoid using the faridfromage package and monitor your dependencies for any malicious activity. You can also use tools like Vulert to check your package-lock.json for vulnerabilities without requiring access to the code or installation.
Conclusion
The faridfromage package poses a significant risk to npm users due to its malicious code that can compromise the integrity of the npm registry. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure your project remains secure.
See every vulnerability recorded for faridfromage →
FAQ
The faridfromage package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall the faridfromage package immediately and monitor your project for any signs of malicious activity.
You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using just your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
