Which versions of spellcheckpy are malicious?

The following PyPI versions of spellcheckpy are flagged malicious: 1.1.0, 1.2.0. Treat any of these as compromised.

How do I remediate spellcheckpy if I installed it?

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

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

Yes — spellcheckpy 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 spellcheckpy 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 spellcheckpy (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spellcheckpy across your stack and pipelines.

Malicious package

spellcheckpyPyPI

Malicious code in spellcheckpy (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-441

Immediate action

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

pip uninstall spellcheckpy

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

2 flagged

1.1.01.2.0

Indicators of compromise (SHA-256)

063d67bbc510966bb83b63d1ba79a8279cf212b9028005800d6f2f99534eec46

cfd5a033715b89d667fb2b3d63b55b7cfbe0476dd277d6fbffe53e1a18415d50

623cdd159f33f5102e70fd0b181c201c98ded82ac4f58f4dac059ecabd2a37a8

d8e8295735de44b251965d6a6f2bc4658bddb0f849a5da14020da6069aa6827d

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 spellcheckpy (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spellcheckpy across your stack and pipelines.
If you installed it — respond
spellcheckpy 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 spellcheckpy 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 spellcheckpy 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. spellcheckpy on PyPI has been identified as a malicious package (versions 1.1.0, 1.2.0 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 spellcheckpy-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