Which versions of pyvantq are malicious?

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

How do I remediate pyvantq if I installed it?

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

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

Yes — pyvantq is associated with the RLMA-2024-11144, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00675 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 pyvantq 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 pyvantq (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 pyvantq across your stack and pipelines.

Malicious package

pyvantqPyPI

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

MAL-2024-11687

Immediate action

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

pip uninstall pyvantq

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)

cb20833846623c9de93008578bd287c7e7beff71c520d250255ea089c081e0b0

0d92efaee175debd7cb98bd61a40ea5acbacb3af5efac81a32b55fe314467b02

a6c5b2c1c554a0ffc8e3b4fd9ea4e9abbf3c9773146ceacbf17557b044032dd2

2708be745317d5a526c18b8398ecb252896f4fd8b9d4cf4855ca5711db0de67f

fa83f50f28b78840cdec84cee94ceae840f86b7f8074e7b9a67c386b6f917ca0

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 pyvantq (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 pyvantq across your stack and pipelines.
If you installed it — respond
pyvantq 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 pyvantq 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 pyvantq 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. pyvantq 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-111442024-08-embeds-RealtekHDAudioManagerRLUA-2026-00675

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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