Which versions of tlask are malicious?

The following PyPI versions of tlask are flagged malicious: 3.1.3, 3.1.4. Treat any of these as compromised.

How do I remediate tlask if I installed it?

Remove tlask from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is tlask part of a known attack campaign?

Yes — tlask is associated with the 2026-06-compr-woodpecker campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect tlask in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking tlask and packages like it before any post-install script runs.

Malicious package

tlaskPyPI

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

MAL-2026-5305

Immediate action

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

pip uninstall tlask

What this malware does

Typosquatting package published from a compromised account with an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution.

It seems to be related to the recent Mini Shai Hulud campaign.

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

Campaign: 2026-06-compr-woodpecker

Reasons (based on the campaign):

compromised-package
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-credentials
abuses-pth
obfuscation
infostealer
The package contains code to detect if it is running in a sandbox environment.
exfiltration-crypto
files-exfiltration
destructive-actions

Malicious versions

2 flagged

3.1.33.1.4

Indicators of compromise (SHA-256)

2b3ae446f7b8d808b84c157ec455883e0bc45e4f4180e51c5cd42ff9852712a2

48854e09c8c33d4501b05aba0583a0b5f91b464d31416749145cc93dbe241f6e

ce8a41bbeaf104368bb005074cd508599f5dd2b95206692ff23bf459915084e5

Frequently asked questions

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

Campaign

2026-06-compr-woodpecker

References

Credits

Kamil Mańkowski (kam193) · reporter

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection