Which versions of dftester-pip are malicious?

The following PyPI versions of dftester-pip are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate dftester-pip if I installed it?

dftester-pip establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed dftester-pip — how do I know if it already compromised me?

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

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

Malicious package

dftester-pipPyPI

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

MAL-2024-11575

Immediate action

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

pip uninstall dftester-pip

What this malware does

Example package with overwritten install command and the reverse shell

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-dftester-pip

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8370ad2a7375101a6442064130e71846a3243c72a42b5d4686b0d3e18251ba8a

2ecd5f09f0c86ff90b26880e231db33f48a7e9712c9a90b8cef385b3e746cbe7

2e23c327cc9243e5437e6b31224c6796b90399065b451269641911b1d1982483

46a51890b899cc8b9991886ea11cfe5b01c2e87d3f410224e60ee0021d6b08b9

1b3ebb681d19b048e9c3e67fd485cb7f44fa76af6a34f8c34067ab4d9fd081a0

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dftester-pip (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dftester-pip across your stack and pipelines.
If you installed it — respond
dftester-pip establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If dftester-pip 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 dftester-pip 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. dftester-pip on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-110232024-11-dftester-pipRLUA-2026-00264

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks dftester-pip-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring