lium-io-gztensorPyPI
Advisory published Updated
lium-io-gztensor is a confirmed malicious PyPI package (MAL-2026-55) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.3, 0.0.5, 4.96). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in lium-io-gztensor (PyPI)
What this malware does
This is a typosquatting/dependency confusion package that is part of a campaign embedding malicious code but was found before the malicious code was injected.
Packages in this campaign clone a legitimate library and add a hidden code that downloads a malicious script. The script then downloads an archive with malicious executable in the version appropriate to the system architecture, and ensures persistency by adding automatically started service entries. The remote code is a Go-based inforstealer and backdoor previously attributed to Nordkorean cybercrime activities. In this campaign, the malicious code is not immediately introduced in the typosquatted package, but added with an update.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-01-gztensor-cli
Reasons (based on the campaign):
-
crypto-related
-
action-hidden-in-lib-usage
-
Downloads and executes a remote executable.
-
clones-real-package
-
peristence-autorun
-
typosquatting
-
obfuscation
-
backdoor
-
infostealer
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for lium-io-gztensor (3 malicious versions).
If you installed it — respond
lium-io-gztensor is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If lium-io-gztensor was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks lium-io-gztensor-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.