Which versions of pytest-tt-ddriven are malicious?

The following PyPI versions of pytest-tt-ddriven are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate pytest-tt-ddriven if I installed it?

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

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

Yes — pytest-tt-ddriven is associated with the RLMA-2025-00501, 2024-11-0wn-sh, RLUA-2026-00651 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 pytest-tt-ddriven 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 pytest-tt-ddriven (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pytest-tt-ddriven across your stack and pipelines.

Malicious package

pytest-tt-ddrivenPyPI

Malicious code in pytest-tt-ddriven (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-960

Immediate action

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

pip uninstall pytest-tt-ddriven

What this malware does

Importing the module triggers sending out the hostname to the package author. It looks to be a placeholder/pentest activity related to BytedDance.

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-0wn-sh

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.

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

9114d3163eeedf4bdc08fdc4bc2c18eaecdf47f9103a57fb7ffc9381c24b2d1f

d24f2acb5da3a402f12260aeadc37c990cc6cba86288fabc77d7e241fe874c90

0fc281f8b24ee3d2420a1c1b3815d5c6a9a9420e0baebe4ea975d530181606a0

31b8ac83cf2d4f5727e603a1a0491e9aa22c120093080155062726d05224848a

7ef48d1ead1815eb277ed33fdf2a4d98d5506ba3fe9d281f6bcfeceda166bc0d

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

Campaign

RLMA-2025-005012024-11-0wn-shRLUA-2026-00651

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks pytest-tt-ddriven-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