Which versions of rtxt-dep1 are malicious?

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

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

Remove rtxt-dep1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed rtxt-dep1 — how do I know if it already compromised me?

If rtxt-dep1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is rtxt-dep1 part of a known attack campaign?

Yes — rtxt-dep1 is associated with the RLMA-2025-04249 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-dep1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rtxt-dep1 (version 0.1).

Malicious package

rtxt-dep1PyPI

rtxt-dep1 is a confirmed malicious PyPI package (MAL-2025-41754) that executes malicious code on install (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rtxt-dep1 (PyPI)

MAL-2025-41754

Immediate action

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

pip uninstall rtxt-dep1

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

18bc8823405495a2b0aaa8e071820b779b6bd145a449c658ad4ac970fe1b099c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for rtxt-dep1 (version 0.1).
If you installed it — respond
Remove rtxt-dep1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If rtxt-dep1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. rtxt-dep1 on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04249

Credits

ReversingLabs · finder

Detect & block this

O3 blocks rtxt-dep1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database