Live › package › MAL-2026-16203
Go to dashboardNot triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-10-26 20:51 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| faiss-cpu-avx512 | pypi | = 1.9.0; = 1.9.1; = 1.9.2; = 1.9.3; = 1.9.4; = 1.9.5; = 1.9.6; = 1.9.7 | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
[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.
This page as .md · .json · in your agent: get_signal("MAL-2026-16203")