Which versions of smtmlib are malicious?

The following PyPI versions of smtmlib are flagged malicious: 0.1.6, 0.1.7. Treat any of these as compromised.

How do I remediate smtmlib if I installed it?

smtmlib 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 smtmlib — how do I know if it already compromised me?

If smtmlib 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.

Is smtmlib part of a known attack campaign?

Yes — smtmlib is associated with the 2025-12-smtblib 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 smtmlib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for smtmlib (2 malicious versions).

Malicious package

smtmlibPyPI

Advisory published Dec 29, 2025Updated Feb 26, 2026

smtmlib is a confirmed malicious PyPI package (MAL-2025-192958) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.6, 0.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in smtmlib (PyPI)

MAL-2025-192958

Immediate action

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

pip uninstall smtmlib

What this malware does

Malicious copy of a standard library module that during class initialization downloads and executes remote code and after that attempts to cover its tracks by overwriting itself with non-malicious code. The remote code aims to collect and exfiltrate sensitive Telegram session files.

This campaign shares infrastructure and basic methods with previous 2025-11-uzip campaign.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-12-smtblib

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
infostealer
target:telegram
exfiltration-credentials
action-hidden-in-lib-usage
covering-tracks
clones-real-package
typosquatting

Malicious versions

2 flagged

0.1.60.1.7

Indicators of compromise (SHA-256)

e871336d0effe99cb62efeda3a287186e75c1bd4ca5770efd81718db8ababe4e

559f20d21d779f510ddc066c1034bc709432b68ce948c92ffd4adc9a2a35bdb7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for smtmlib (2 malicious versions).
If you installed it — respond
smtmlib 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 smtmlib 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

No. smtmlib on PyPI has been identified as a malicious package (versions 0.1.6, 0.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-12-smtblib

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks smtmlib-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

Explore

All malware advisories How O3 detects malware Vulnerability database