Which versions of ezauto are malicious?

The following PyPI versions of ezauto are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate ezauto if I installed it?

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

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

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

Malicious package

ezautoPyPI

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

MAL-2024-10027

Immediate action

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

pip uninstall ezauto

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4137fe5a1afbfe98e5e628680fde6b83c0afbae76e3111db8ef689e0bf1a51fb

ff3b8efbe807b1064cbb66731803f7902c852b132e15703e66339c5ecb1d8444

4d5e63bafe0b12244a82ffbde9bcf5eaf32ba47034bcd84168efb7f9e2becf9a

224c565837d2f0c6513fdfff8607b4953b90d086c6a252787dbda85f4ea582e2

9be20ee87250b9246a68063957074a5656dfc51458e6a1d7c455076b5b99e874

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

Campaign

RLMA-2024-082622024-08-embeds-RealtekHDAudioManagerRLUA-2026-00307

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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