Which versions of aiosignalasync are malicious?

The following PyPI versions of aiosignalasync are flagged malicious: 0.1, 0.2, 0.3. Treat any of these as compromised.

How do I remediate aiosignalasync if I installed it?

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

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

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

Malicious package

aiosignalasyncPyPI

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

MAL-2025-2931

Immediate action

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

pip uninstall aiosignalasync

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

3 flagged

0.10.20.3

Indicators of compromise (SHA-256)

8cf4c55bccc5b335d30e8ded5d48bb998df404ec25feaa195f43018ea3ac7413

15a13f445d9786154344091a65a4a83c89c0683abaabbebe7539879856d2735d

5f77ce31a234eb422ebfaa8182ea066bd7c10c154bfefb76757b0c06bbd3e655

3013fed20d2b81a81d6f8bfdeb0f9fe2daeeff8207e133034cd9ea1b1a6b6487

7b11c5974fbfac911e459d8fbcd2127121cb4c3ff9840f7ce22d3001d046de6c

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

Campaign

RLMA-2025-019292025-02-multisRLUA-2026-00047

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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