Malicious Code Detected in ffg-env Package: Security Alert

ffg-env Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20427: Malicious code in ffg-env (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 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

The ffg-env package is an npm library designed to facilitate environment variable management in Node.js applications. It allows developers to easily configure and manage environment settings, which is crucial for application deployment and operation. However, this package has been identified to contain malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the ffg-env package arises from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in 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 ffg-env

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, users can remove the ffg-env package from their project until a secure version is released. This can be done by executing the command: 'npm uninstall ffg-env'. Consider using alternative packages for environment variable management that do not have known vulnerabilities.

Conclusion

The ffg-env package has been identified to contain malicious code that poses a serious security risk to applications using it. Users are urged to update or remove the package to safeguard their projects. Regular monitoring of dependencies and utilizing tools like Vulert can help maintain application security.

See every vulnerability recorded for ffg-env →

Share this vulnerability

FAQ

ffg-env is an npm package used for managing environment variables in Node.js applications.

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

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Currently, there is no patched version available. Users should monitor updates from the package maintainers.

If immediate updates are not possible, consider removing the package and using alternative solutions for managing environment variables.

How To Fix

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

npm uninstall ffg-env

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