Malicious code in saeka (PyPI)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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: amazon-inspector (5416f158a10ecc0060a14b69d40032c44a6613599ebe37c322b81cf2451cd260) The saeka CLI provisions an Xray multi-protocol proxy (VLESS/VMess/Trojan/Shadowsocks with hardcoded password/id 'saeka') on the installer's own GCP Cloud Run account…

Published by the source

14 Oct 2026, 21:33 UTC

Last modified by the source

29 Oct 2026, 14:30 UTC

Source last checked

30 Oct 2026, 06:40 UTC

1. Revision 1 · created · 30 Oct 2026

   Published from osv record MAL-2026-17877

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: mal-2026-17877

Advisory: Malicious code in saeka (PyPI)
IDs: mal-2026-17877
Record: https://patchnext.com/advisories/mal-2026-17877 (revision 1, source checked 30 Oct 2026, 06:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI saeka: affected >= 1.0.0, <= 1.0.0; >= 1.2.0, <= 1.2.0; >= 1.2.1, <= 1.2.1; >= 1.2.2, <= 1.2.2; >= 1.2.3, <= 1.2.3; >= 1.3.0, <= 1.3.0; >= 1.4.0, <= 1.4.0; >= 1.5.0, <= 1.5.0; >= 1.6.0, <= 1.6.0; >= 1.7.0, <= 1.7.0; >= 1.8.0, <= 1.8.0; >= 1.8.1, <= 1.8.1; >= 1.8.2, <= 1.8.2; >= 2.0, <= 2.0; >= 4.0, <= 4.0; >= 5.0, <= 5.0; >= 6.0, <= 6.0; >= 7.0, <= 7.0; >= 8.0, <= 8.0; >= 9.0, <= 9.0; >= 9.5, <= 9.5; >= 10.0, <= 10.0; >= 11.1, <= 11.1; >= 11.2, <= 11.2; >= 11.9, <= 11.9; >= 15.0, <= 15.0

## Suggested inspection (read-only)
- `python -m pip show saeka`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on saeka.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-17877 (OSV record MAL-2026-17877 lists affected ranges: PyPI saeka >=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 =9.5 =10.0 =11.1 =11.2 =11.9 =15.0 <=15.0)

Commands are suggestions: review each one before running it.