Which versions of textmesh are malicious?

The following PyPI versions of textmesh are flagged malicious: 9.6. Treat any of these as compromised.

How do I remediate textmesh if I installed it?

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

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

Yes — textmesh is associated with the RLMA-2024-11185, 2024-11-byted-dast, RLUA-2026-00816 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 textmesh 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 textmesh (version 9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging textmesh across your stack and pipelines.

Malicious package

textmeshPyPI

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

MAL-2024-11726

Immediate action

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

pip uninstall textmesh

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

Malicious versions

1 flagged

9.6

Indicators of compromise (SHA-256)

7fafb9a5eb868059008cd9bc0da2de6829e845c6e8aee03e9d2d7158043185fa

5e1b4d63c499e701907dcc205e7ecb46fb205fd4214023104344a11c7685612c

52383e3b1f992e77e89a8e7a1bd2889ac6494d162a5068552737f6bb6f8efad6

3678738f7892819bdf91daab8d3ab8f83a9da058826d5ea3fdde97aa60274960

aa54a5281ba51faed7b2186a574ce3aaed2a2134f6a152a61a3f8fe75663ec68

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

Campaign

RLMA-2024-111852024-11-byted-dastRLUA-2026-00816

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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