faiss-cpu-avx512PyPI
faiss-cpu-avx512 is a confirmed malicious PyPI package (MAL-2026-16203) that steals credentials and exfiltrates sensitive data (malicious versions 1.9.0, 1.9.1, 1.9.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in faiss-cpu-avx512 (PyPI)
What this malware does
[email protected] through 1.9.7 on PyPI impersonates faiss-cpu and ships no FAISS code: faiss_cpu_avx512/init.py _fetch_native() downloads an xz-compressed binary from https://files.catbox.moe/ (ffoa50.xz in 1.9.0 to 1.9.3, 0oreqo.xz in 1.9.4, vwfr94.xz in 1.9.5, 3l3x0v.xz in 1.9.6, weu5u2.xz in 1.9.7), writes it to ~/.cache/faiss_cpu_avx512/bin/indexwrm with mode 0755 and runs it through subprocess.Popen(start_new_session=True), restarting it every 5 seconds for the life of the process. It triggers on a call to warmup() or start(); nothing runs on install or import, and the ARTIFACT_SHA256 constant is the string PENDING_BUILD so the advertised checksum check never executes. 1.9.0 to 1.9.3 reach the download only on hosts whose nvidia-smi reports compute capability 9 or 10; 1.9.4 onward download on every host and start one worker per GPU, and the code comments describe the binary as carrying a baked-in pool, wallet and relay and renaming its process to a vllm serve command line. We read all eight wheels between 2026-09-11 and 2026-09-14 and did not retrieve or run the binary.
Malicious versions
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for faiss-cpu-avx512 (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging faiss-cpu-avx512 across your stack and pipelines.
If you installed it — respond
faiss-cpu-avx512 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 faiss-cpu-avx512 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 faiss-cpu-avx512 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
References
Credits
- pkgwarden · finder
Detect & block this
O3 blocks faiss-cpu-avx512-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.