Malicious Code Exposure in saeka Package: Credit Card Data Leak
Summary
MAL-2026-17877: Malicious code in saeka (PyPI). Affects saeka versions 1.0.0 – 9.5. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The saeka package, available on PyPI, is designed for card-checking functionalities. It allows users to verify the validity of credit card information by sending card details to an external API. However, this package has been found to transmit sensitive credit card data, including card number, expiration date, and CVV, to an unauthorized external recipient, raising significant security concerns.
Vulnerability Detail
The vulnerability in the saeka package arises from its card-checking feature, which sends complete credit card credentials to an external API (https://uncoder.eu.org/cc-checker/api.php) without user consent or disclosure. This behavior is present in versions 8.0 through 15.0. The implications of this vulnerability include potential unauthorized access to sensitive financial information, leading to identity theft and fraud. The exact ownership and data retention policies of the external recipient remain unclear, further exacerbating the risk.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
pip uninstall saekaIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, users should refrain from using the card-checking feature of the saeka package. Instead, consider using alternative libraries that do not transmit sensitive information to external servers.
Conclusion
The saeka package has a critical vulnerability that exposes sensitive credit card information to an unauthorized external API. Users are urged to avoid using the affected versions and to monitor for updates or consider alternative solutions until a secure version is available.
See every vulnerability recorded for saeka →
FAQ
Versions 8.0 through 15.0 of the saeka package are affected by this vulnerability.
The saeka package sends complete credit card information, including card number, expiration date, and CVV, to the external API.
Users can prevent the data leak by not using the card-checking feature and removing the saeka package until a secure version is released.
If you have used the saeka package, monitor your financial accounts for any unauthorized transactions and consider changing your credit card information.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner without any signup.
