Which versions of rtxt-dep4 are malicious?

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

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

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

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

Yes — rtxt-dep4 is associated with the RLMA-2025-04251, GENERIC-standard-pypi-install-pentest, RLUA-2026-00737 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-dep4 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-dep4 (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-dep4 across your stack and pipelines.

Malicious package

rtxt-dep4PyPI

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

MAL-2025-41756

Immediate action

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

pip uninstall rtxt-dep4

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)

5ac2183c6350abdc5136f80cebf1085710658fec002d33bb4bf24b12cac2b911

5dbc56b495d2b0738f85f3e15260a463d4b3821d3ce14443e11aa851fb6cf28b

927a9dbf7483280f63719ca53cf98986f15e2244e8108ae037557ab2d728de75

5e77495ccf93d28e5d2b7a5e16bf04cc8f3083dcc8f55561b5540afc1effe2e2

87a303bcf8c3e686e883da643bbd32cc1096bbcb6b5f95b5c351acca8c5f94f7

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-dep4 (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-dep4 across your stack and pipelines.
If you installed it — respond
rtxt-dep4 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-dep4 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-dep4 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-dep4 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-04251GENERIC-standard-pypi-install-pentestRLUA-2026-00737

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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