Which versions of aioasyncsqlite are malicious?

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

How do I remediate aioasyncsqlite if I installed it?

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

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

Yes — aioasyncsqlite is associated with the RLMA-2025-02553, 2025-04-aiolitesql, RLUA-2026-00039 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 aioasyncsqlite 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 aioasyncsqlite (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 aioasyncsqlite across your stack and pipelines.

Malicious package

aioasyncsqlitePyPI

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

MAL-2025-4203

Immediate action

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

pip uninstall aioasyncsqlite

What this malware does

Clone of aiosqlite with hidden exfiltration of selected data during "executeall" query (see L59-97)

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

Campaign: 2025-04-aiolitesql

Reasons (based on the campaign):

clones-real-package
action-hidden-in-lib-usage
exfiltration-generic

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

36eac4e94422bad683a266f6ab17477b4e148af05a80f4ce6e986164ec050609

ba581055511e650dc4e94c5398391a1a00a49666c47fd2054c2176246439cae1

9dabf7e852a633394c9df21ee491c5a3582e2c172c624fd2b48cc127dbdc410a

abcad47d9de6fd22670e3162b610f32da3ee3ac4c516063b154a8bac9fa545f6

c6374e24a8fa121736af3592b71d27fe4b92056d52b4d4e36504e4a07034bbef

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 aioasyncsqlite (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 aioasyncsqlite across your stack and pipelines.
If you installed it — respond
aioasyncsqlite 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 aioasyncsqlite 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 aioasyncsqlite 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. aioasyncsqlite 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

RLMA-2025-025532025-04-aiolitesqlRLUA-2026-00039

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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