Which versions of tonetext are malicious?

The following PyPI versions of tonetext are flagged malicious: 0.1.1, 0.2.1. Treat any of these as compromised.

How do I remediate tonetext if I installed it?

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

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

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

Malicious package

tonetextPyPI

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

MAL-2025-191906

Immediate action

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

pip uninstall tonetext

What this malware does

When imported, the code embedded into the exception class downloads a remote file, and runs it by importing, and attempts to cover tracks by overwriting itself, removing caches and other related files.

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

Campaign: 2025-03-tonetext

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
obfuscation

Malicious versions

2 flagged

0.1.10.2.1

Indicators of compromise (SHA-256)

6bdd482d6ab1a67e92e07cfac1da64aa0d02a55c6f019ca1f3fdadc87ecf2e4c

c46725ad6c88079cce4f7fa4a29175fec7f78ea83344da99d0f02ac4f020fcf3

59e36377e7671291e506fade84e8d65b72afebad7c5e5fca51c5111ec9afe2ca

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 tonetext (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tonetext across your stack and pipelines.
If you installed it — respond
tonetext 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 tonetext 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 tonetext 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. tonetext on PyPI has been identified as a malicious package (versions 0.1.1, 0.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-03-tonetext

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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