Which versions of iterquarry are malicious?

The following PyPI versions of iterquarry are flagged malicious: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2.0, 2.2.1. Treat any of these as compromised.

How do I remediate iterquarry if I installed it?

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

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

Yes — iterquarry is associated with the 2026-10-iterquarry 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 iterquarry across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for iterquarry (6 malicious versions).

Malicious package

iterquarryPyPI

Advisory published Oct 21, 2026Updated Oct 21, 2026

iterquarry is a confirmed malicious PyPI package (MAL-2026-18131) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.1, 2.1.2, 2.1.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in iterquarry (PyPI)

MAL-2026-18131

Immediate action

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

pip uninstall iterquarry

What this malware does

In this campaign, one package (iterquarry) holds an encrypted payload, while another one (libseal) provides algorithms to decrypt and execute it. In earlier versions, the code used an embedded key and the payload was contacting a Discord bot. Starting with iterquarry 2.2.0, the key to the encrypted payload is not embedded and the payload remains unknown.

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

Campaign: 2026-10-iterquarry

Reasons (based on the campaign):

obfuscation
The malicious code is intentionally included in a dependency of the package
action-hidden-in-lib-usage

Malicious versions

6 flagged

2.1.12.1.22.1.32.1.42.2.02.2.1

Indicators of compromise (SHA-256)

229de224c9319ae50283d0c8fb0f76e351d82327ac204193b7dd2d62026ee41d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for iterquarry (6 malicious versions).
If you installed it — respond
iterquarry 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 iterquarry 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. iterquarry on PyPI has been identified as a malicious package (versions 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2.0, 2.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-iterquarry

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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