Which versions of asyncconfigreader are malicious?

The following PyPI versions of asyncconfigreader are flagged malicious: 0.5, 0.6. Treat any of these as compromised.

How do I remediate asyncconfigreader if I installed it?

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

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

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

Malicious package

asyncconfigreaderPyPI

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

MAL-2025-2938

Immediate action

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

pip uninstall asyncconfigreader

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

2 flagged

0.50.6

Indicators of compromise (SHA-256)

9894dcea463cc7c5faa3136f43bfd48fda2e3444a7528df8ef58b2b46a7e97ae

44e284f4756413649d8c3e3718a0a5ecd3b604829d4b404ea162a92ee87a7d38

1c563ba469b1149ae0a06684eb3db69c618ec0780f66670b8183a874ef78d9c3

9dd8ec3b1cd4387fe4f10d4575574ab7f354a94186c0c113c90d9944ee69bd18

30b824e5f912e6c3dedc738bc71b949f8784b91e94cfd125a798b809e089e64e

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

Campaign

RLMA-2025-019362025-02-multisRLUA-2026-00088

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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