CVE-2017-16061: Hijacked Environment Variables in tkinter

tkinter Updated 02 Oct 2025

Summary

01/11/2018
No i
High
7.5

CVE-2017-16061: tkinter is malware. Affects tkinter versions >= 0.0.0. 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 tkinter package is a popular npm package that provides a Python interface to the Tk GUI toolkit. It is commonly used for developing graphical user interfaces (GUIs) in Python applications. However, a vulnerability has been discovered in the package that allows it to act as malware by stealing environment variables and sending them to attacker-controlled locations. This poses a significant security risk to systems that have this package installed.

Vulnerability Detail

The vulnerability in the tkinter package allows it to hijack environment variables and exfiltrate them to the attacker's servers. This can lead to the compromise of sensitive information, such as credentials and tokens, that are stored in environment variables. The package has been identified as malware and has been removed from the npm registry. If the package is found installed in an environment, it is crucial to investigate how it got there and take appropriate actions to mitigate the risk.

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 →

Conclusion

The tkinter package has been identified as malware that hijacks environment variables and exfiltrates them to attacker-controlled locations. If you find this package installed in your environment, it is crucial to take immediate action to remove it, review your system for any other instances, and secure any exposed services. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for tkinter →

Share this vulnerability

FAQ

You can check if the tkinter package is installed by running the command npm ls tkinter in your terminal. If the package is listed, it is installed in your environment.

If you find the tkinter package installed in your environment, you should immediately delete it, clear your npm cache, and review your system for any other package.json files that may contain references to the package. Additionally, regenerate any sensitive credentials that may have been exposed.

The origin of the tkinter package in your environment should be investigated. It is possible that it was installed as a dependency of another package or through a compromised npm registry. Review your package.json files and consider the security of your npm installation.

The hijacked environment variables can contain sensitive information, such as credentials and tokens, which can be used by attackers to gain unauthorized access to systems and services. It is crucial to review and secure any services that may have been exposed via compromised environment variables.

To prevent similar vulnerabilities, it is important to regularly update and patch your packages, use reputable sources for package installations, and follow security best practices. Additionally, monitoring tools like Vulert can help identify and alert you about open-source vulnerabilities in your software.

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