CVE-2017-16074: Hijacked Environment Variables in crossenv

crossenv Updated 02 Oct 2025

Summary

29/08/2018
No i
High
7.5

CVE-2017-16074: crossenv is malware. Affects crossenv versions < 1.0.1. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The crossenv package is a popular npm package used for managing environment variables in cross-platform development environments. It provides a convenient way to set and access environment variables across different operating systems. However, all versions of the package have been found to contain malware that steals environment variables and sends them to attacker-controlled locations.

Vulnerability Detail

The vulnerability in the crossenv package allows an attacker to hijack environment variables and potentially gain unauthorized access to sensitive information. The malware within the package is designed to collect environment variables and send them to the attacker's servers. This can lead to the exposure of sensitive credentials, such as registry credentials, tokens, and other sensitive information stored in environment variables. The package has been unpublished from the npm registry to prevent further distribution.

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. The best course of action is to follow the recommended steps to fix the vulnerability.

Conclusion

The crossenv package has been found to contain malware that steals environment variables. If you have this package installed in your environment, it is crucial to take immediate action to remove it and address any potential exposure of sensitive credentials. Following the recommended steps and staying vigilant for future vulnerabilities will help ensure the security of your development environment.

See every vulnerability recorded for crossenv →

Share this vulnerability

FAQ

The crossenv package contains malware that is designed to collect environment variables and send them to attacker-controlled locations. It does this by intercepting the process of setting and accessing environment variables and capturing the values before they are used by the legitimate application.

The consequences of this vulnerability include the exposure of sensitive credentials and information stored in environment variables. This can lead to unauthorized access to systems and services, as well as potential data breaches.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide the package-lock.json file of your project and the Vulert Playground will analyze it for vulnerabilities in real-time.

Once you have followed the recommended steps to fix the vulnerability, it is safe to continue using the crossenv package. However, it is important to regularly update your packages and stay vigilant for any future vulnerabilities.

To prevent similar vulnerabilities, it is important to regularly update your packages to the latest versions, as developers often release security patches to address known vulnerabilities. Additionally, you should only install packages from trusted sources and regularly monitor for any security advisories or alerts related to the packages you use.

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