Which versions of textwrap-toolkit are malicious?

The following PyPI versions of textwrap-toolkit are flagged malicious: 1.2.2. Treat any of these as compromised.

How do I remediate textwrap-toolkit if I installed it?

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

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

Yes — textwrap-toolkit is associated with the 2026-05-ninja-core-utils 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 textwrap-toolkit 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 textwrap-toolkit (version 1.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging textwrap-toolkit across your stack and pipelines.

Malicious package

textwrap-toolkitPyPI

Malicious code in textwrap-toolkit (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3407

Immediate action

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

pip uninstall textwrap-toolkit

What this malware does

During installation, obfuscated code exfiltrates cryptocurrency wallet data to a hardcoded location and places a backdoor through a new authorized SSH key. Information about the placed backdoor is sent back to the attacker, and sshd configuration is adjusted to ensure the successful remote connection.

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

Campaign: 2026-05-ninja-core-utils

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation
crypto-related
exfiltration-crypto
backdoor

Malicious versions

1 flagged

1.2.2

Indicators of compromise (SHA-256)

029e190fc99763d65a096339b29fa85aeb0a23c3818a632a2dd4dc99f3e8fd64

56384f41b38b4a58c1bfaface12044e42992f75079eb548a41a954584977952e

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

Campaign

2026-05-ninja-core-utils

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks textwrap-toolkit-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