Which versions of collects are malicious?

The following PyPI versions of collects are flagged malicious: 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate collects if I installed it?

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

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

Yes — collects is associated with the 2025-11-spellcheckers 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 collects across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for collects (3 malicious versions).

Part of a larger attack: 2025-11-spellcheckers published 28 malicious packages. See the full campaign →

Malicious package

collectsPyPI

Advisory published Mar 11, 2026Updated Oct 30, 2026

collects is a confirmed malicious PyPI package (MAL-2026-1341) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in collects (PyPI)

MAL-2026-1341

Immediate action

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

pip uninstall collects

What this malware does

Packages contain hidden code that is effectively run during importing or using the library, and downloads second stage code. Then, a process running in background periodically connects to a remote host and waits for next code to execute

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

Campaign: 2025-11-spellcheckers

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote malicious script.
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

3 flagged

1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

fc7f98d0c4c092f4eb4a73240f8c7a5df90717853ee408fefa9eeb09a41d2cae

660c692db664fe8287c8465077a8bcd73b16a3ecbcfdd69aa9ff45c1ca83d24c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for collects (3 malicious versions).
If you installed it — respond
collects 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 collects 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. collects on PyPI has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-11-spellcheckers

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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