Which versions of spellcheckerpy are malicious?

The following PyPI versions of spellcheckerpy are flagged malicious: 1.0.0, 1.1.0, 1.3.0. Treat any of these as compromised.

How do I remediate spellcheckerpy if I installed it?

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

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

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

Malicious package

spellcheckerpyPyPI

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

MAL-2026-375

Immediate action

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

pip uninstall spellcheckerpy

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 the next code to execute.

The malicious code was in version 1.3.0, but the package itself was clearly uploaded with malclious intentions.

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.01.1.01.3.0

Indicators of compromise (SHA-256)

2ffcd3e16661799d1a55e0d5e359ffd6fb883256310f280d6e0b88a5edb4e626

79cc4c6495567fe7659e9e4bb5964727bf95cfc9f78d32209937d73457bd476b

10bb96df7d43eff438bbe7a555c333f9e1d02f837ee3636dcbf9aa9e22175c48

14f2a6cb3c370817d9494648c7f7f19714f6b8985d936fe93d0d1685cd522fb2

0812165e8c72368e5a52652b3e4ebad7b61dd0bee3368dbd47b8728ca2eaeaad

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

Detect & block this

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