Which versions of lium-4-96 are malicious?

The following PyPI versions of lium-4-96 are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate lium-4-96 if I installed it?

lium-4-96 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.

I already installed lium-4-96 — how do I know if it already compromised me?

If lium-4-96 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is lium-4-96 part of a known attack campaign?

Yes — lium-4-96 is associated with the 2026-01-gztensor-cli campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find lium-4-96 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lium-4-96 (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lium-4-96 across your stack and pipelines.

Malicious package

lium-4-96PyPI

Malicious code in lium-4-96 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-54

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall lium-4-96

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

1 flagged

0.0.3

Indicators of compromise (SHA-256)

f30524e8a9ff2b7c5b43b57ea582beeba9d8f94da4097ecd572d26b4177e6626

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lium-4-96 (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lium-4-96 across your stack and pipelines.
If you installed it — respond
lium-4-96 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-4-96 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks lium-4-96 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. lium-4-96 on PyPI has been identified as a malicious package (version 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-01-gztensor-cli

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks lium-4-96-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring