Which versions of testt-test are malicious?

The following PyPI versions of testt-test are flagged malicious: 1.0.2, 9.1.3, 99.0.1. Treat any of these as compromised.

How do I remediate testt-test if I installed it?

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

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

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

Malicious package

testt-testPyPI

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

MAL-2025-47802

Immediate action

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

pip uninstall testt-test

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

3 flagged

1.0.29.1.399.0.1

Indicators of compromise (SHA-256)

e0f4204db839fa47f3d8716648c68973831be4d84ebbac8905801ee856acfdc9

ae5c6866f6b5709adfcc4c703d80e4b78438e4278ecc2d6797b1477c646b3419

05bfc8616802c80804de7998c57d6b1f62deff849f9d3545b0775edfcd0de264

e3e0756cee3997a64425dcb3b3936cb3001413457babfb9beb4be7c7f2d37265

6ac0ba0de12962897e6e5038b3227d3b003655443a57a425d386f5017dd41416

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

Campaign

RLMA-2025-04812GENERIC-standard-pypi-install-pentestRLUA-2026-00813

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks testt-test-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