MATCH Melelery/c-binance-futures-quant — This repository is a Binance futures trading bot framework that contains hardcoded real credentials including Alibaba Cloud API keys, OSS credentials, a MySQL database password, and Feishu (Lark) API secrets.
MATCH Badrulamin42/Centoc — Repository contains hardcoded Binance Futures API key and secret in a PHP webhook file, used to query order history on fapi.binance.com.
MATCH Melelery/binance — This repository contains a Binance trading server with multiple hardcoded real credentials: Aliyun API keys, MySQL database credentials, Feishu/Lark app secrets, and OSS authentication keys. It also handles Binance API keys stored in a database.
MAYBE instasec567/crydhrutitest — Repository contains commented-out ccxt initialization code with what appear to be real Bybit and Binance API credentials hardcoded in a trading bot's route file.
MAYBE rosavskiy/AiCryptoBot — The repository contains what appear to be real Bybit API credentials (API key and secret) hardcoded in a documentation file, though they are commented out as part of a migration guide from Bybit to Binance testnet.
MATCH ronalzhang/Jesse — Repository contains hardcoded OKX exchange API credentials (API key, secret key, and passphrase) in a system documentation/troubleshooting file (SYSTEM_ISSUES_SOLUTIONS.md).
MATCH mlisboa17/R7_V3 — This repository contains hardcoded Binance API keys and secrets committed directly in a user-data.sh script for an automated crypto trading bot.
MATCH r00tkidTR/CoinBot — This repository contains a Binance futures trading bot with hardcoded real API keys, secret keys, and Telegram bot tokens directly in the source code.
MATCH azeezkareem58-star/Trad — Bybit trading bot with hardcoded API key and secret directly in the source code (bybit_client.py), not using environment variables or placeholders.
MAYBE tjrwhd9075/telegramAlarmBot — Repository contains hardcoded Bybit API credentials and a Telegram bot token in a trading bot, though the Bybit keys are marked as testnet (test=True).
MATCH adityaapraveen/Crypto-EMA-Bot — Repository contains hardcoded Bybit API credentials in a ccxt trading bot script, with what appear to be real API keys committed directly in the source code.
MATCH opeyemi09/bybit_grid_bot — This repository contains a Bybit grid trading bot with hardcoded API credentials (API key, API secret, and Telegram bot token) in the default config object of advancebot.js.
MATCH Hongshen-Yang/okx-hsyquant0 — This OKX trading bot repository contains real leaked API credentials visible in the notebook output, including the API key, signature, and passphrase.
MATCH girishimpx/imperial_backend — Backend for an exchange trading platform ('Imperial Exchange') with hardcoded OKX API credentials directly in the source code (creonjob.js).
MATCH marcellinamichie291/Kucoin-2 — Repository contains hardcoded KuCoin API credentials (API key, secret, and passphrase) and a Telegram bot token in a Java trading bot that monitors KuCoin price movements.
MAYBE mwlang/crypto — The README contains what appear to be real API keys and secrets for Bittrex, Coinbase, GDAX, Binance, and Cobinhood exchanges, hardcoded in the example configuration shown in the documentation.
MATCH skedzior/arbitron-ecs — Repository contains hardcoded KuCoin exchange API credentials (API key, secret, and passphrase) in an Elixir module for a blockchain state indexer/arbitrage tool.
MATCH Ritenoob/kucoin-futures-dashboard — Repository contains a plaintext file 'KuCoin live API credentials.txt' with what appear to be real KuCoin Futures API credentials (API key, secret, and passphrase) committed directly to the repository.
MAYBE gate/gatews — Gate.io WebSocket SDK example file contains hardcoded API key and secret that appear to be real credentials rather than obvious placeholders.
MAYBE Aetf/GateTrader — The README contains what appears to be a real Gate.io API key leaked via environment variable display: `b8ffbcfa3e8eafc345ade75f84c4a490` shown in the help text as the current env value for KEY.
MATCH staccDOTsol/EthTokenArbTradingNode — This repository contains a cryptocurrency arbitrage trading bot with hardcoded Poloniex API keys and secrets directly in the source code.
MATCH shert391/bot-arbitrage — Repository contains hardcoded MEXC exchange API credentials directly in source code for an arbitrage bot.
MATCH servrox-solutions/panana-predictions — Repository contains hardcoded MEXC exchange API credentials (API key and secret) in a TypeScript file used for fetching price data for a prediction market platform.
MATCH zentai/bayes_excersice — This repository contains a trading bot for Huobi/HTX exchange with hardcoded API keys and secrets in at least two source files.
MAYBE viennamania/owinwallet — Repository contains hardcoded OKX API credentials in a commented-out code block, including an API key, secret key, and passphrase.
MAYBE viennamania/damoa-wallet — Repository contains hardcoded OKX API credentials in commented-out code, including an API key, secret key, and passphrase that appear to be real credentials.
MAYBE viennamania/damoa-wallet-bangbang — The repository contains hardcoded OKX API credentials in a commented-out code block within route.ts, including an API key, secret key, and passphrase.
MATCH Hudie/crypto_algo_trading — This repository contains hardcoded Deribit exchange API credentials (client ID and secret) in a trading bot's market data service file.
MAYBE maestro73/Bitgain_Full — Repository contains hardcoded Deribit and BitMEX API credentials in trading bot/arbitrage code, though the default API URL points to test.deribit.com suggesting these may be testnet keys.
MATCH adrianwenc/MAC1_config — Repository contains a committed config file with real Deribit production API credentials (client ID and secret) for a trading bot, with test mode set to false.
MAYBE DovaX/deribit_easy_api — The README contains hardcoded Deribit API credentials (client_id: 'dgVf4SU3', client_secret: 'fxy1PNb2PCYS7a4neMBklGh1utJJd1jerBNoxVFGdE') labeled as 'TEST API' in the usage example.
MAYBE Cieloc/boltCOT — Repository contains a hardcoded Deribit API key in the source code, though the API secret is left empty. This is a partially leaked credential for the Deribit exchange.
MAYBE Aieyup/MITQuantsystem — The repository's env.example file contains what appear to be real Deribit API credentials (client ID and secret) committed directly. The Binance keys appear to be encrypted (Fernet/gAAAAAB prefix), but the Deribit credentials look like genuine plaintext API keys.
MAYBE stradle/options-aggregator — Repository contains commented-out Deribit API credentials (client_id and client_secret) in source code that appear to be real credentials rather than placeholders.
MAYBE manish-gkv/TestDeribit — Repository contains hardcoded Deribit API credentials (client_id and client_secret) in a C++ trading bot that connects to Deribit's WebSocket API.
MATCH EdipMangtay/PPO_Financal_Algorithm — Repository contains hardcoded Binance Futures API key and secret in config.py for a PPO-based crypto trading bot.
MAYBE staccDOTsol/updatedprovebot — This repository contains hardcoded OKEx API keys and secrets as fallback values in okex.js, used in a market maker/trading bot with ccxt library initialization.
MATCH CryptoRobotFr/1-create-personnal-trading-bot — This repository contains a Jupyter notebook with hardcoded FTX exchange API credentials (api_key and api_secret) that appear to be real, as evidenced by successful trade execution output in the notebook.
MATCH mattsahr/star-atlas-dash — This repository contains hardcoded FTX exchange API credentials (API key and secret) in the source code file `src/data/fetch-ftx.js`.
MATCH AdrienGavazzi/big_data — This repository contains a Jupyter notebook with hardcoded FTX exchange API credentials in a trading bot. The API key 'xL6SYTqmHtawoCaihqkoqlCtW_q_vfJ6-xVZlnh6' and secret 'em2tgTy47IblAubmT18_yIAMwzDVXoTnM2hHCvWm' are committed in plain text.
MATCH kkminseok/binance_NFT — Repository contains hardcoded FTX exchange API credentials (API key and secret) in the FtxClient class initialization in pycode/main.py.
MATCH nar789/coinlabmodels — Repository contains hardcoded BitMEX API credentials in trading bot code, with API key 'mRFAH87bvrET5B7kJ1OQz3JX' and secret 'auENVlHIN-qMGsNQB7ebm7qWGg_riiYh3yhdNPiMPKnb2Jvd' used directly in __main__ blocks.
MATCH icofy-io/satoshimars — This repository contains a BitMEX trading bot with hardcoded API key and secret directly in the source code (satoshimars_ml.py).
MAYBE Abhisheksoni1/BitmexBot — BitMEX trading bot with what appear to be real API credentials hardcoded in settings.py.example - a BitMEX API key and secret that don't look like obvious placeholders.
MATCH RetributionByRevenue/ETH-USD-Bitmex-Trading-Bot-Preconfigured-Python-Environment- — This repository contains a BitMEX trading bot with hardcoded API keys and secrets directly in the source code, representing real leaked exchange credentials.
MATCH mjgpinheiro/Physics_models — Repository contains hardcoded BitMEX API credentials (API key and secret) in a Jupyter notebook implementing a BTC trading bot with SMA crossover strategy.
MATCH Stuchbery/Reinforcement-Learning-Market-Entry — Repository contains hardcoded BitMEX API credentials (both live mainnet and testnet) in a reinforcement learning trading bot for BTC/USD market entry.
MATCH RetributionByRevenue/___Live-Updating-Website-4-Bitcoin-Algorithm___ — This repository contains a BitMEX trading bot with hardcoded API keys and secrets directly in the Python source code.
MAYBE Blankeeir/coinbase_hft — A Coinbase International Exchange HFT bot that has committed log files containing a partially leaked API key ('Uw5h...') and evidence of real production authentication attempts against live exchange servers.