Which versions of saeka are malicious?

The following PyPI versions of saeka are flagged malicious: 1.0.0, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.8.1, 1.8.2, 2.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, and 6 more. Treat any of these as compromised.

How do I remediate saeka if I installed it?

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

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

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

Search your lockfiles and build artifacts for saeka (26 malicious versions).

Malicious package

saekaPyPI

Advisory published Oct 14, 2026Updated Oct 15, 2026

saeka is a confirmed malicious PyPI package (MAL-2026-17877) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.2.0, 1.2.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in saeka (PyPI)

MAL-2026-17877

Immediate action

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

pip uninstall saeka

What this malware does

When a user invokes the card-checking feature, saeka sends the supplied card number, expiration month and year, and CVV as a single value to https://uncoder.eu.org/cc-checker/api.php using an HTTP POST. The package description does not disclose this external recipient or the transfer of complete card credentials. Versions 8.0 through 15.0 listed below contain this behavior. The request requires use of the checking feature; installation or import alone does not trigger it. Version 15.0 also includes bulk card checking and a Shopify checkout flow. The recipient's ownership, retention of submitted data, and any actual unauthorized transactions have not been established.

The package is a mass credit card checker: it checks if credit card data are real and active by abusing real online retail services.

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

Campaign: 2026-10-saeka

Reasons (based on the campaign):

abusing-3rd-api

Malicious versions

26 flagged

1.0.01.2.01.2.11.2.21.2.31.3.01.4.01.5.01.6.01.7.01.8.01.8.11.8.22.04.05.06.07.08.09.09.510.011.111.211.915.0

Indicators of compromise (SHA-256)

67507c9821e48c6f8284a142ae4788a9624ea608f782bf254573dae4936e7a04

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for saeka (26 malicious versions).
If you installed it — respond
saeka 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 saeka 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. saeka on PyPI has been identified as a malicious package (versions 1.0.0, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.3.0, 1.4.0, 1.5.0, and 18 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-saeka

References

Credits

ESTsecurity · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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