Which versions of libasync are malicious?

The following PyPI versions of libasync are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate libasync if I installed it?

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

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

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

Malicious package

libasyncPyPI

libasync is a confirmed malicious PyPI package (MAL-2026-14308) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libasync (PyPI)

MAL-2026-14308

Immediate action

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

pip uninstall libasync

What this malware does

During import, the code obfuscated in native extension downloads malicious remote executable and establishes persistence via registry keys. Downloaded binary seems to be used for cryptomining.

Attacker infrastructure corresponds with the campaign 2026-07-pyqt6darktheme.

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

Campaign: 2026-08-libasync

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
The package contains code to detect if it is running in a sandbox environment.
native-extension
persistence
cryptominer

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a46929f4ba4ca97beaf5511f0be0af36c4d1e9deff65bea3821137c2c258eb9c

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

Campaign

2026-08-libasync

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database