Malicious Code Injection in lium-io-gztensor Package - A Critical Vulnerability

lium-io-gztensor Updated 05 Jan 2026

Summary

05/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-55: Malicious code in lium-io-gztensor (PyPI). Affects lium-io-gztensor versions 0.0.3 – 4.96. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The lium-io-gztensor package is a Python library available on PyPI, designed to facilitate tensor operations and computations. However, it has been identified as a typosquatting package that mimics a legitimate library, embedding malicious code aimed at compromising user systems. This vulnerability poses significant risks to users who may unknowingly install the package, as it can lead to unauthorized access and data theft.

Vulnerability Detail

The vulnerability stems from a malicious campaign that utilizes typosquatting techniques to create a deceptive package. The lium-io-gztensor package was found to clone a legitimate library and embed hidden code that downloads a malicious script. This script subsequently retrieves an archive containing a malicious executable tailored to the system architecture, ensuring persistence by creating automatically started service entries. The malicious code is linked to a Go-based infostealer and backdoor, previously associated with North Korean cybercrime activities. The threat is exacerbated by the fact that the malicious code is not present in the initial package but is introduced through updates.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall lium-io-gztensor

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

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

Workaround

As a workaround, users can monitor their systems for any unauthorized processes or services that may have been created by the malicious code. It is advisable to run antivirus scans and check for any unusual network activity that may indicate a compromise.

Conclusion

The lium-io-gztensor package has been identified as a malicious entity that poses significant risks to users through its embedded malicious code. It is crucial for users to uninstall this package and remain vigilant about the sources from which they install software. Utilizing tools like Vulert can enhance security by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for lium-io-gztensor →

Share this vulnerability

FAQ

Typosquatting is a malicious practice where attackers create fake packages that closely resemble legitimate ones, hoping users will mistakenly install them due to typographical errors.

You can check your installed packages by running the command pip list in your terminal. Look for 'lium-io-gztensor' in the list.

If you suspect a compromise, immediately disconnect from the internet, run a full antivirus scan, and consult with a cybersecurity professional for further assistance.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software. You can use the Vulert playground to check if your application is affected by this vulnerability.

The risks include unauthorized access to sensitive data, installation of backdoors, and potential data theft, which can have severe implications for both individuals and organizations.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall lium-io-gztensor

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

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