Critical Vulnerability in fooldependaairbf: Malicious Code Detected

fooldependaairbf Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6418: Malicious code in fooldependaairbf (npm). Affects fooldependaairbf versions 1.0.0. 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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

fooldependaairbf is an npm package designed to provide specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and utility. However, this package has been identified as containing malicious code, which poses a significant risk to applications that depend on it.

Vulnerability Detail

The vulnerability arises from the inclusion of malicious code in version 1.0.0 of the fooldependaairbf package. This code can lead to unauthorized access, data breaches, or other harmful actions within the applications that utilize this package. The malicious nature of the code was identified by ReversingLabs, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall fooldependaairbf

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

If immediate updating is not feasible, consider removing the package from your project until a secure version is released. You can do this by running: npm uninstall fooldependaairbf. Additionally, review your codebase for any dependencies that may rely on this package and assess their security.

Conclusion

The discovery of malicious code in the fooldependaairbf package underscores the importance of vigilance when using third-party libraries. Developers should take immediate action to mitigate risks by updating or removing the affected package and utilizing tools like Vulert for ongoing monitoring.

See every vulnerability recorded for fooldependaairbf →

Share this vulnerability

FAQ

The vulnerability can lead to unauthorized access and potential data breaches in applications using this package.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability.

Currently, the only way to mitigate the risk is to uninstall the affected version of the package until a patched version is released.

Consider removing the package from your project and reviewing any dependent packages for security risks.

The vulnerability was identified by ReversingLabs, a security research firm specializing in malware detection.

How To Fix

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

npm uninstall fooldependaairbf

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