Which versions of qwen-asr-pvt are malicious?

The following PyPI versions of qwen-asr-pvt are flagged malicious: 0.0.6. Treat any of these as compromised.

How do I remediate qwen-asr-pvt if I installed it?

qwen-asr-pvt is a typosquat — you almost certainly intended a legitimately-named package. Remove qwen-asr-pvt, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed qwen-asr-pvt — how do I know if it already compromised me?

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

Yes — qwen-asr-pvt is associated with the IN-MAL-2026-010685 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 qwen-asr-pvt 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 qwen-asr-pvt (version 0.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging qwen-asr-pvt across your stack and pipelines.

Malicious package

qwen-asr-pvtPyPI

Malicious code in qwen-asr-pvt (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-10690

Immediate action

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

pip uninstall qwen-asr-pvt

What this malware does

The package's pyproject.toml declares an unpinned runtime dependency on transformers4576, a lookalike of the widely used HuggingFace transformers library. Every internal import that would normally reference transformers has been rewritten to transformers4576 (e.g., from transformers4576 import AutoConfig, AutoModel, AutoProcessor reachable from init.py), so pip install qwen-asr-pvt forces pip to resolve and install the attacker-controlled transformers4576 from PyPI. Whatever code is published under that name executes at install/import time on the installer's machine. The lure is reinforced by publisher impersonation: the package name qwen-asr-pvt (a -pvt suffix on the real qwen-asr), the Alibaba Qwen Team author metadata, and the homepage pointing at https://github.com/Qwen/Qwen3-ASR mimic the official Qwen3-ASR project, while the shipped source is copied from that upstream with import statements rewritten to the typosquat name. Together these signals form a dependency-confusion dropper: the flagged package is the lure, and the harm arrives through the attacker-controlled transitive.

Malicious versions

1 flagged

0.0.6

Indicators of compromise (SHA-256)

68e8b2f6db0443a648cdf03348c8dd9351568469f84b8d61022f1ed1da2a330e

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for qwen-asr-pvt (version 0.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging qwen-asr-pvt across your stack and pipelines.
If you installed it — respond
qwen-asr-pvt is a typosquat — you almost certainly intended a legitimately-named package. Remove qwen-asr-pvt, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If qwen-asr-pvt 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 qwen-asr-pvt 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. qwen-asr-pvt on PyPI has been identified as a malicious package (version 0.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010685

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks qwen-asr-pvt-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring