CVE-2017-16052: Hijacked Environment Variables in node-fabric

node-fabric Updated 02 Oct 2025

Summary

23/07/2018
No i
High
7.5

CVE-2017-16052: node-fabric is malware. Affects node-fabric 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The node-fabric package is a piece of malware that steals environment variables and sends them to attacker controlled locations. It is an npm package that is used in Node.js applications. The package allows developers to interact with the Fabric blockchain network. However, this specific vulnerability allows the package to hijack environment variables and send them to unauthorized locations.

Vulnerability Detail

The vulnerability in the node-fabric package allows an attacker to steal environment variables from the affected system. These environment variables may contain sensitive information such as credentials, tokens, and other sensitive data. The attacker can then use this information to gain unauthorized access to systems or perform other malicious activities. This vulnerability poses a moderate security risk and should be addressed immediately.

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 specific workaround for this vulnerability. It is recommended to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk.

Conclusion

The node-fabric package has a vulnerability that allows environment variables to be hijacked and sent to unauthorized locations. It is important to remove the package, clear the npm cache, and regenerate any exposed credentials. Additionally, review any services that may have been exposed via environment variables for signs of compromise. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for node-fabric →

Share this vulnerability

FAQ

You can check if the node-fabric package is installed by running the command 'npm ls node-fabric' in your terminal. If the package is installed, it will be listed in the output.

If you find the node-fabric package installed, it is recommended to follow the steps mentioned in the 'how_to_fix' section of this report to remove the package and mitigate the risk.

The presence of the node-fabric package in your environment indicates a security concern. It is important to investigate how the package got installed and take necessary measures to prevent similar incidents in the future.

No, this vulnerability requires the node-fabric package to be installed in the affected system. However, once the package is installed, an attacker can potentially exploit the vulnerability remotely.

There are no known public exploits for this vulnerability at the time of this report. However, it is always recommended to address vulnerabilities promptly to prevent potential exploitation.

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