Which versions of asynctestpython are malicious?

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

How do I remediate asynctestpython if I installed it?

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

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

Yes — asynctestpython is associated with the RLMA-2025-01937, 2025-02-multis, RLUA-2026-00092 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 asynctestpython 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 asynctestpython (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging asynctestpython across your stack and pipelines.

Malicious package

asynctestpythonPyPI

Malicious code in asynctestpython (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2939

Immediate action

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

pip uninstall asynctestpython

What this malware does

Infostealer with multiple possibilities, but not auto-activating on installation. There are already multiple attempts to publish it, with different innocent-looking names.

The campaign contains the with Infostealer itself and packages that include it as dependency and triggered.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-02-multis

Reasons (based on the campaign):

infostealer
The malicious code is intentionally included in a dependency of the package

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

929e7aac59882b3f73eae18de1a5e7777a84a4711f64e8fab23136014a349d73

4859350d7ee0a4b1299d33326c0fe69656ee4fa8bca791ab0533e97e821e4347

fd21bb1c5c93539b976f7a2d7083394bebaacea6ca24c52cebf7b292798158a7

85db75678f8f5ee43347ea2ab5f0aa3cd8cebafa896635990bcc3ac37da32610

730cd7be175c8c84aa10759bcc2e46ad9173bf38d20dc15daa968c0778de468d

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 asynctestpython (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging asynctestpython across your stack and pipelines.
If you installed it — respond
asynctestpython 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 asynctestpython 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 asynctestpython 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. asynctestpython 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-019372025-02-multisRLUA-2026-00092

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks asynctestpython-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