Which versions of queeuees are malicious?

The following PyPI versions of queeuees are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate queeuees if I installed it?

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

If queeuees was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is queeuees part of a known attack campaign?

Yes — queeuees is associated with the 2026-09-queeuees, IN-MAL-2026-021233 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 queeuees across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for queeuees (version 0.0.1).

Malicious package

queeueesPyPI

Advisory published Sep 29, 2026Updated Oct 8, 2026

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

Malicious code in queeuees (PyPI)

MAL-2026-17286

Immediate action

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

pip uninstall queeuees

What this malware does

Queeuees 0.0.1 ships two top-level packages, Queeuees and Queues, with byte-identical init.py files. Each init.py assembles a byte blob from concatenated hex/tuple/rotated-byte literals and decodes it through bit-rotation, XOR keystream, seeded Fisher-Yates, inverse S-box, and LCG XOR stages. The result is passed to builtins.exec at import time via getattr(import('builtins'), 'exec')(payload), where the strings 'builtins' and 'exec' are hidden as byte arrays XORed with 75. Execution is triggered by a descriptor set_name hook that fires when the containing class is defined during module import, so import Queeuees or import Queues runs the decoded code. Identifiers use homoglyph-style names (_0I1IIO, _lIII1, _OI110l, _01I0) and cover-story labels ('Module signature database', 'Certificate fingerprint lookup table'), while the published metadata advertises the package as 'a very basic calculator'. The Queeuees name resembles the common word 'Queues' with duplicated vowels, and the identical payload under both names broadens the typo-catchment surface for the same import-time dropper.

Obfuscated code iterates over files in the system and adds a comment to every .py file found.

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

Campaign: 2026-09-queeuees

Reasons (based on the campaign):

obfuscation
modify-system-without-consent

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1adc88dd9031dc991006afcf10242d1de3aa7994f6bcb4542faed95524d6ebe0

f793adc7f1d26294831307abed18a284d7834d8e4733a8b05d9863bf2d70c60d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for queeuees (version 0.0.1).
If you installed it — respond
queeuees 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 queeuees was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. queeuees on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-queeueesIN-MAL-2026-021233

References

Credits

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

Detect & block this

O3 blocks queeuees-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