Which versions of snap-queue are malicious?

The following PyPI versions of snap-queue are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate snap-queue if I installed it?

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

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

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

Malicious package

snap-queuePyPI

snap-queue is a confirmed malicious PyPI package (MAL-2026-16408) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in snap-queue (PyPI)

MAL-2026-16408

Immediate action

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

pip uninstall snap-queue

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

62bf582784fd41b3484157f6454ddcb6ab2ae10a5d93abeb19a5bfa5642b7e64

66d21211753dd05cd26db975d94b4567f80e382f6bbfef1f3202595e73a20724

e0bb29642def9150e89bacf4da4e1a64f7bc972cd145053cbb0feee0baa768f3

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 snap-queue (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging snap-queue across your stack and pipelines.
If you installed it — respond
snap-queue 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 snap-queue 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 snap-queue 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. snap-queue on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-snap-queueIN-MAL-2026-020329

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks snap-queue-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

Explore

All malware advisories How O3 detects malware Vulnerability database