Which versions of pyaacv are malicious?

The following PyPI versions of pyaacv are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate pyaacv if I installed it?

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

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

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

Malicious package

pyaacvPyPI

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

MAL-2024-11667

Immediate action

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

pip uninstall pyaacv

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.1

Indicators of compromise (SHA-256)

c124dbb2081c9e37a80d3dbc6ea5fc8d8cb741b93921ba10cc7ba837db96cd8a

a2b1eae89b2113e331866b1b5c59e25fad6beac680864bd87fffded0854617bb

97316284f3bcbee8c6a3d552b10137107cc84af73e858048147ed6973fe9ea6c

6df8d929eda34f484a8a67ca1e86398c3f6494c9ff086469980af0da82dfa48d

30ec0598b12a12f403b3878096e5ac7d5c5fb0e7100245807a187b1532f2fb81

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

Campaign

RLMA-2024-111242024-08-embeds-RealtekHDAudioManagerRLUA-2026-00619

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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