CVE-2017-16069: Hijacked Environment Variables in nodeffmpeg

nodeffmpeg Updated 02 Oct 2025

Summary

29/08/2018
No i
High
7.5

CVE-2017-16069: nodeffmpeg is malware. Affects nodeffmpeg versions < 1.0.2. 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 nodeffmpeg package is a piece of malware that steals environment variables and sends them to attacker controlled locations. It is an npm package that has been unpublished from the npm registry. This package is considered malware and should not be installed in any environment. If found installed, it is important to determine how it got there and take appropriate actions to secure the environment.

Vulnerability Detail

The vulnerability in the nodeffmpeg package allows for the hijacking of environment variables. This means that sensitive information stored in environment variables can be stolen and sent to the attacker's controlled locations. The impact of this vulnerability can be severe, as it can lead to the compromise of sensitive credentials and the exposure of services that rely on these credentials, such as databases. The package has been identified as malware and should be removed immediately from any environment.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to remove the nodeffmpeg package and take the necessary steps to secure the environment.

Conclusion

The nodeffmpeg package is a piece of malware that steals environment variables and should not be installed in any environment. If found installed, it is crucial to remove the package, secure the environment, and regenerate any compromised credentials. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for nodeffmpeg →

Share this vulnerability

FAQ

The nodeffmpeg package is a piece of malware that steals environment variables and sends them to attacker controlled locations.

You can check for the presence of the nodeffmpeg package by inspecting your package.json files or by using package management tools like npm.

If you find the nodeffmpeg package installed, you should immediately delete it, clear your npm cache, remove it from any other package.json files, and regenerate any sensitive credentials that may have been exposed.

After removing the nodeffmpeg package, you should review and secure any services that may have been exposed via compromised credentials. This includes regenerating credentials, tokens, and ensuring proper access controls are in place.

The nodeffmpeg package vulnerability can lead to the compromise of sensitive credentials and the exposure of services that rely on these credentials, such as databases. This can result in unauthorized access, data breaches, and other security incidents.

How To Fix

No fixed version is published for this vulnerability.

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