CVE-2017-16054: Hijacked Environment Variables in nodefabric

nodefabric Updated 02 Oct 2025

Summary

23/07/2018
No i
High
7.5

CVE-2017-16054: nodefabric is malware. Affects nodefabric 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 nodefabric 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 designed to compromise the security of the environment it is installed in by extracting sensitive information from the environment variables.

Vulnerability Detail

The vulnerability in the nodefabric package allows attackers to hijack environment variables and exfiltrate them to their own controlled locations. This can lead to the exposure of sensitive credentials and other confidential information. The package acts as a malware and poses a significant security risk to the affected environment. It is crucial to identify how the package was installed and take appropriate measures to mitigate the impact.

How To Fix

No fixed version is published for this vulnerability.

To fix the vulnerability, follow these steps:

  1. Delete the nodefabric package from your environment.
  2. Clear your npm cache to ensure no remnants of the package remain.
  3. Check all package.json files on your system to ensure the package is not present in any other dependencies.
  4. Regenerate any sensitive credentials, tokens, or registry credentials that may have been exposed.
  5. Review any services that may have been exposed via credentials in your environment variables, such as databases, for indicators of compromise.

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

Conclusion

The nodefabric package is a malware that compromises the security of the environment by stealing environment variables. If you find this package installed in your environment, it is crucial to take immediate action to remove it and mitigate the impact. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for nodefabric →

Share this vulnerability

FAQ

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

You can check for the presence of the nodefabric package by inspecting your installed packages or searching for it in your package.json files.

The vulnerability in the nodefabric package can lead to the exposure of sensitive credentials and other confidential information, which can be used by attackers for malicious purposes.

To mitigate the impact, you should delete the package, clear your npm cache, ensure it is not present in any other package.json files, and regenerate any exposed credentials. Additionally, review any services that may have been exposed via credentials in your environment variables.

If you find the nodefabric package installed in your environment, you should follow the steps mentioned in the 'how_to_fix' section to remove the package and mitigate the impact.

How To Fix

No fixed version is published for this vulnerability.

To fix the vulnerability, follow these steps:

  1. Delete the nodefabric package from your environment.
  2. Clear your npm cache to ensure no remnants of the package remain.
  3. Check all package.json files on your system to ensure the package is not present in any other dependencies.
  4. Regenerate any sensitive credentials, tokens, or registry credentials that may have been exposed.
  5. Review any services that may have been exposed via credentials in your environment variables, such as databases, for indicators of compromise.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.