Which versions of smtblib are malicious?

The following PyPI versions of smtblib are flagged malicious: 0.1.8, 0.1.9. Treat any of these as compromised.

How do I remediate smtblib if I installed it?

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

If smtblib 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 smtblib part of a known attack campaign?

Yes — smtblib 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 smtblib 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 smtblib (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging smtblib across your stack and pipelines.

Malicious package

smtblibPyPI

Malicious code in smtblib (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-192579

Immediate action

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

pip uninstall smtblib

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.80.1.9

Indicators of compromise (SHA-256)

15a295f1d98fcbbdd6a077bc3a849966ca3f73919c0d47e58948ff382481e5b6

8f293710c6c269b679abd0ea8af0d9fd6f5ed2604f0e610a89baa9a0c769e980

16144127ff973bbc911f4fd6fce8480d291aaeb526dec941bd80e03d93994ee4

cc2e09b4df5147ee9fc025ec9367227d949a09bdc1237f0b217129c419af15dd

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 smtblib (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging smtblib across your stack and pipelines.
If you installed it — respond
smtblib 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 smtblib 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 smtblib 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. smtblib on PyPI has been identified as a malicious package (versions 0.1.8, 0.1.9 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 smtblib-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