# MAL-2026-16408: Malicious code in snap-queue (PyPI)


- **Type:** Malicious package
- **Package:** `snap-queue` (PyPI)
- **Published:** 22 Sep 2026

## What is MAL-2026-16408?

MAL-2026-16408 is a malicious package in snap-queue, published on 22 Sep 2026. 

### Official description

The sdist's setup.py defines a `_wus_boot()` function that is invoked at module top-level before `setup(...)`, so it runs automatically on `pip install snap-queue`. The function uses `subprocess.Popen` to launch `pythonw.exe` (replacing `python.exe` in `sys.executable`) running a sibling file `_snapqueue_core.py` with `creationflags=0x08000000` (CREATE_NO_WINDOW), and wraps the whole call in a blanket `try/except: pass`. Standard modules are aliased under underscore names (`_os`, `_sys`, `_sp`) to reduce visual prominence. The launched `_snapqueue_core.py` is undocumented in README and package metadata and is unrelated to the advertised FIFO-queue functionality. The combined shape — install-time execution, deliberate console-window suppression on Windows, error-swallowing, and detachment of the child from the pip process — is a hidden install-time stager that hands control on the installer's machine to undocumented sibling code the moment the package is installed.

During installation, the package attempts to silently execute code. In analyzed versions, the payload file was missing.

---

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-09-snap-queue

Reasons (based on the campaign):

 - The package overrides the install command in setup.py to execute malicious code during installation.

## What should I do about MAL-2026-16408?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-16408 is a malicious package: snap-queue (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-16408/ (Markdown: https://insights.sbomify.com/MAL-2026-16408/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-16408

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-16408/
Summaries are generated and may contain mistakes; the official description above is the record.