Which versions of rtxt-dep3 are malicious?

The following PyPI versions of rtxt-dep3 are flagged malicious: 3.3.7. Treat any of these as compromised.

How do I remediate rtxt-dep3 if I installed it?

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

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

Yes — rtxt-dep3 is associated with the RLMA-2025-04250, GENERIC-standard-pypi-install-pentest, RLUA-2026-00736 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 rtxt-dep3 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 rtxt-dep3 (version 3.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rtxt-dep3 across your stack and pipelines.

Malicious package

rtxt-dep3PyPI

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

MAL-2025-41755

Immediate action

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

pip uninstall rtxt-dep3

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

3.3.7

Indicators of compromise (SHA-256)

6bb8cf9565491216972397193b19116a7d443f32ae4680722f8c259abd60611c

72cd069f18d09ad432d06e3ef414186794031c4d5856346d49b480ad4adb5302

c9452c218f473489657ae73882d2b63b23ea6349c2d4da8bf5fe393f9ef69bbf

d8dd6cf72aea24d8c771e739fcef15a3f1738ffdfefcd04a7cc0a4c45e049717

b8314e14047b65604b20626eec1c14be2ce3e2aa7073bc45f35d022d423e926b

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

Campaign

RLMA-2025-04250GENERIC-standard-pypi-install-pentestRLUA-2026-00736

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks rtxt-dep3-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