Malicious Code Injection in faridfrites: npm Package Vulnerability
Summary
MAL-2025-171203: Malicious code in faridfrites (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 'faridfrites' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary functionality of 'faridfrites' is not well-defined, as it is primarily used to inflate developer reputation scores through automated publishing scripts. This vulnerability poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in the 'faridfrites' package originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The malicious payload can affect any project that inadvertently includes this package, leading to security risks and reputation damage for developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall faridfritesIf 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, avoid using the 'faridfrites' package and consider using 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 that may indicate the presence of malicious packages.
Conclusion
The 'faridfrites' package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for faridfrites →
FAQ
'faridfrites' is an npm package identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.
You should uninstall the package immediately using the command: npm uninstall faridfrites.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Check out the Vulert playground at Vulert Scanner.
Yes, consider using other reputable npm packages that provide similar functionality without the associated risks.
