Which versions of binance-sdk-ebate are malicious?

The following PyPI versions of binance-sdk-ebate are flagged malicious: 10.0.0. Treat any of these as compromised.

How do I remediate binance-sdk-ebate if I installed it?

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

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

Yes — binance-sdk-ebate is associated with the RLMA-2025-04746, GENERIC-standard-pypi-install-pentest, RLUA-2026-00148 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 binance-sdk-ebate 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 binance-sdk-ebate (version 10.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging binance-sdk-ebate across your stack and pipelines.

Malicious package

binance-sdk-ebatePyPI

Malicious code in binance-sdk-ebate (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47747

Immediate action

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

pip uninstall binance-sdk-ebate

What this malware does

Example of typosquatting package, with rather safe using localhost as exfiltration target. Package targets a typo in the Binance documentation: https://github.com/binance/binance-connector-python/blob/f1703c54c3059423a8568b2300597210b19b938e/clients/rebate/docs/migration_guide_rebate_sdk.md

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

10.0.0

Indicators of compromise (SHA-256)

8c6df72dfa3549c1d5f204b74c7ddea64781cedd2b93ee103698a72b587e1301

00215dfec61ee883c8bdcaf36ceda21926774db797421144e2cb673eb30956f7

43db9ff01b53b59066c74bb7571e281c1364444174851bd25c272e8fd7f3f503

a85059f412b3df3d86b1d2905b67aaf4e1e3d1f2b0585171a44f598a5106011d

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 binance-sdk-ebate (version 10.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging binance-sdk-ebate across your stack and pipelines.
If you installed it — respond
binance-sdk-ebate 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 binance-sdk-ebate 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 binance-sdk-ebate 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. binance-sdk-ebate on PyPI has been identified as a malicious package (version 10.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04746GENERIC-standard-pypi-install-pentestRLUA-2026-00148

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks binance-sdk-ebate-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