Which versions of aiotrans are malicious?

The following PyPI versions of aiotrans are flagged malicious: 1, 1.0.0, 1.0.0rc1, 1.0.0rc2, 1.1, 1.2. Treat any of these as compromised.

How do I remediate aiotrans if I installed it?

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

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

Yes — aiotrans is associated with the RLMA-2024-07805, 2024-08-uconst-old, RLUA-2026-00049 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 aiotrans 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 aiotrans (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aiotrans across your stack and pipelines.

Malicious package

aiotransPyPI

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

MAL-2024-9938

Immediate action

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

pip uninstall aiotrans

What this malware does

Package "uconst" is the package containing malicious code with multiple stage, exfiltrating basic info as well as browser data. It's put into others as dependency.

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

Campaign: 2024-08-uconst-old

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
The malicious code is intentionally included in a dependency of the package
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

6 flagged

11.0.01.0.0rc11.0.0rc21.11.2

Indicators of compromise (SHA-256)

82b53f190a9dab4c137995ef38a2d8ae2fbb1c767df25d78947617b4cd13eb40

e0498376a1c30a968d829de5eaa50fa25237b442db00223b5e151f2d57804ad9

3bd64da5911ab6ec28e1bc33993b363b52702ff6bb19a87b98f37267d0784664

bb8cf3d7bd77381552e649ff04268517f8189a6fcf9e1b9d404a82b2f58c173c

70f61a6b3743cf8f886a3ee4e8cb22c3d5224e95e367af3ebf038841435fc7c3

ff2245ffeac219b2e96d82132c1461c69613599da5fa2de1d152e8b6423314a2

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

Campaign

RLMA-2024-078052024-08-uconst-oldRLUA-2026-00049

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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