Vulnerabilities

Vulnerability · MAL-2026-17877

Malicious code in saeka (PyPI)

Published Oct 14, 2026 · catalog updated Oct 15, 2026 · Malicious code in saeka

Open the advisory

Exploitation likelihood is not on this record for MAL-2026-17877. A missing EPSS score is not a low risk. Compare Malicious code in saeka with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Malicious code in saeka).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
PyPI saeka

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. --- _-= Per source details. Do not edit below this line.=-_ ## Source: kam193 (67507c9821e48c6f8284a142ae4788a9624ea608f782bf254573dae4936e7a04) 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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • PyPI saeka1.0.0, 1.2.0, 1.2.1

How to fix MAL-2026-17877

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for MAL-2026-17877. A missing EPSS score is not a low risk. Compare Malicious code in saeka with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 1.0.0, 1.2.0, 1.2.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: kam193 (67507c9821e48c6f8284a142ae4788a9624ea608f782bf254573dae4936e7a04) 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 (b

  2. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: kam193 (67507c9821e48c6f8284a142ae4788a9624ea608f782bf254573dae4936e7a04) 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 (b

  3. Oct 15, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    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 us

Sources

References

Freshness

Last verified in this catalog Oct 15, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.