Which versions of asynchelpers are malicious?

The following PyPI versions of asynchelpers are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate asynchelpers if I installed it?

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

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

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

Malicious package

asynchelpersPyPI

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

MAL-2025-1965

Immediate action

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

pip uninstall asynchelpers

What this malware does

Importing the module starts (through init.py) the code that download, extracts and starts a remote executable. This has been identified by any.run as a AsyncRAT. The VirtusTotal detection rate was originally at the edge of false positive, but increased significantly during a few hours.

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

Campaign: 2025-01-asynchelpers

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

3abdfacd480ef37dda3fa5227b950c999e9d6332d4bf65b56e981752a0d4a055

bc72d23ac15ca2bd56b6336b7999972ac306783bb0cacd59b7060304be22bf6e

e262ab4b975a2de9c0216656ca3e760d84f3cdacb526340248dd476c31ddeb0d

99d47d8c6d0c1ac235c1516350bc19073422bcf4c6b8f9b0e16e956a7e230d21

5eb364faa17b6d04d2243f56410fb36a5040aab1d87b818403e3bc03029c8377

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

Campaign

RLMA-2025-012002025-01-asynchelpersRLUA-2026-00089

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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