Critical Malicious Code Vulnerability in Froidz Package

froidz Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20966: Malicious code in froidz (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Froidz package is an npm library designed for various functionalities in JavaScript applications. It is widely used for its ease of integration and utility in enhancing application performance. However, recent findings have revealed that the package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the Froidz package arises from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue originates from version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall froidz

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 Froidz package from your project and replacing it with a safer alternative until a patched version is released. You can do this by executing: 'npm uninstall froidz'.

Conclusion

The discovery of malicious code in the Froidz package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users are urged to take immediate action to mitigate risks associated with this vulnerability.

See every vulnerability recorded for froidz →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications using the Froidz package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.

If immediate updates are not possible, consider removing the Froidz package and using a safer alternative until a patch is available.

Yes, using tools like Vulert can help you monitor your project's dependencies for vulnerabilities in real-time.

Ignoring this vulnerability may lead to severe security breaches, unauthorized access to sensitive data, and potential damage to your application's reputation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall froidz

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback