Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2022-40769---Profanity — Generates cryptocurrency private keys from CVE-2023-39910 (Libbitcoin) and CVE-2022-40769 (Profanity) vulnerabilities. Outputs hex keys for use with blockchain scanners to check balances on affected wallets. | Kitploit
Tools/GitHubGitHub/ethicbrudhack/cve-2022-40769---profanity
Password CrackingVulnerability AnalysisExploitationCryptographyPapers & ResearchLearning & EducationRepository Deleted
GitHubethicbrudhack/cve-2022-40769---profanity

CVE-2022-40769---Profanity

Generates cryptocurrency private keys from CVE-2023-39910 (Libbitcoin) and CVE-2022-40769 (Profanity) vulnerabilities. Outputs hex keys for use with blockchain scanners to check balances on affected wallets.

The upstream repository was not found during the latest Kitploit update check. This listing remains available for reference, but it has been removed from search results.
1223 months agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

DONATE: bc1qps62cyk9f9unmdkc9k3ccj9e2h8ywfhg2j53ec

Built with ❤️ for the crypto research community.

============================================================ CVE-2023-39910 + CVE-2022-40769 - KEY GENERATOR TO TXT

DESCRIPTION: This tool generates private keys from two critical vulnerabilities that affected cryptocurrency wallets. It creates TXT files with hexadecimal private keys (64 chars = 256 bits) that can be fed into AllChainScanner for address generation and balance checking.

🔴 GENERATES KEYS FROM 2 MAJOR CRYPTO VULNERABILITIES!

============================================================ VULNERABILITIES EXPLAINED

  1. CVE-2023-39910 (Libbitcoin Explorer / Milk Sad)

    • Affected: libbitcoin-explorer 3.2.0
    • Weakness: mt19937 RNG seeded with time(nullptr) - only 32 bits
    • Impact: $900,000+ stolen from BTC, ETH, LTC, DOGE, ZEC, DASH
    • Date: 2023
    • Key generation: Direct mt19937 output → 32-byte private key
  2. CVE-2022-40769 (Profanity - Ethereum Vanity Address Generator)

    • Affected: Profanity tool (Ethereum vanity addresses)
    • Weakness: LCG with 32-bit state (state * 1103515245 + 12345)
    • Impact: ~$10,000,000 stolen from Ethereum wallets
    • Date: 2022
    • Key generation: LCG state → 32-byte private key

============================================================ HOW IT WORKS

Step 1: Generate keys ./keygen 0 1000000 keys.txt

Step 2: Output files created

  • libbitcoin_keys.txt (CVE-2023-39910 keys)
  • profanity_keys.txt (CVE-2022-40769 keys)

Step 3: Feed to AllChainScanner ./AllChainScanner -f libbitcoin_keys.txt -o found.txt -t all ./AllChainScanner -f profanity_keys.txt -o found.txt -t all

Step 4: Scanner converts 64-char hex to:

  • Private keys → Public keys → Addresses
  • BTC: 1..., 3..., bc1...
  • ETH: 0x...
  • Checks against blockchain

============================================================ COMPILATION & USAGE

COMPILE: g++ -O3 -march=native -o keygen keygen.cpp -std=c++17

USAGE: ./keygen [start_seed] [end_seed] [output.txt]

PARAMETERS: start_seed Starting seed (default: 0) end_seed Ending seed (default: 1000000) output.txt Output filename (default: keys.txt)

EXAMPLES: ./keygen 0 1000000 keys.txt → Generates 1,000,000 keys (0 to 999,999)

./keygen 1000000 2000000 keys.txt → Generates 1,000,000 keys (1,000,000 to 1,999,999)

./keygen 0 10000000 keys.txt → Generates 10,000,000 keys (takes ~1-2 minutes)

============================================================ OUTPUT FILES

File: libbitcoin_.txt

  • Contains CVE-2023-39910 private keys
  • Format: 64 hex chars per line
  • Example: 2e52a25a5c8b9e4c8f1a2b3c4d5e6f70...

File: profanity_.txt

  • Contains CVE-2022-40769 private keys
  • Format: 64 hex chars per line
  • Example: 8a1b2c3d4e5f6078a9b0c1d2e3f4a5b6...

============================================================ PERFORMANCE

GeneratorSpeed (keys/s)1M keys time10M keys time
CVE-2023-39910~2,000,000~0.5 sec~5 sec
CVE-2022-40769~2,000,000~0.5 sec~5 sec
Combined~1,000,000~1 sec~10 sec

============================================================ INTEGRATION WITH ALLCHAINSCANNER

LINK: https://github.com/ethicbrudhack/AllChainScanner-Bitcoin-eth-zcash-etc..-

  1. Generate keys: ./keygen 0 10000000 keys.txt

  2. Scan Bitcoin keys: ./AllChainScanner -f libbitcoin_keys.txt -o btc_found.txt -t P2PKH ./AllChainScanner -f libbitcoin_keys.txt -o btc_found.txt -t P2SH ./AllChainScanner -f libbitcoin_keys.txt -o btc_found.txt -t bech32

  3. Scan Ethereum keys: ./AllChainScanner -f profanity_keys.txt -o eth_found.txt -t ethereum

  4. Scan all coins: ./AllChainScanner -f libbitcoin_keys.txt -o all_found.txt -t HEX

============================================================ SUPPORTED COINS BY ALLCHAINSCANNER

All keys generated work with: ✅ Bitcoin (1..., 3..., bc1...) ✅ Ethereum (0x...) ✅ Litecoin (L..., M...) ✅ Dogecoin (D...) ✅ Dash (X...) ✅ Zcash (t1..., t3...) ✅ Bitcoin Cash (bitcoincash:...) ✅ BNB Smart Chain (0x...) ✅ Polygon (0x...) ✅ Avalanche C-Chain (0x...)

============================================================ REAL-WORLD IMPACT

CVE-2023-39910 (Milk Sad):

  • Discovered: 2023
  • Vulnerable wallets: Generated by libbitcoin-explorer 3.2.0
  • Stolen amount: $900,000+
  • Affected coins: BTC, ETH, LTC, DOGE, ZEC, DASH
  • Users affected: Thousands

CVE-2022-40769 (Profanity):

  • Discovered: 2022
  • Vulnerable wallets: Ethereum vanity addresses
  • Stolen amount: $10,000,000+
  • Affected coins: ETH, ERC-20 tokens
  • Users affected: Hundreds

============================================================ STATISTICS COMPARISON

VulnerabilityEntropyPossibilitiesTime to Brute Force*
CVE-2023-3991032 bits4.29 × 10^9~8 seconds (24-word)
CVE-2023-3991032 bits4.29 × 10^9~12 minutes (BIP32)
CVE-2022-4076932 bits4.29 × 10^9~8 seconds (24-word)
CVE-2022-4076932 bits4.29 × 10^9~12 minutes (BIP32)
REAL 256-bit256 bits1.16 × 10^77Impossible

*Based on:

  • RTX 4090: 150,000 seeds/sec (24-word mode)
  • RTX 4090: 6,000,000 seeds/sec (BIP32 mode)

============================================================ EXAMPLE OUTPUT

Running: ./keygen 0 5 keys.txt

======================================== CVE-2023-39910 + CVE-2022-40769 - GENERATOR KLUCZY

Zakres: 0 - 5 Liczba kluczy: 5 Plik wyjściowy: keys.txt

[1] CVE-2023-39910 (Libbitcoin/Milk Sad) - generowanie... 5/5 | 2500000 keys/s Zapisano: libbitcoin_keys.txt (0.0s)

[2] CVE-2022-40769 (Profanity) - generowanie... 5/5 | 2500000 keys/s Zapisano: profanity_keys.txt (0.0s)

======================================== ✅ GOTOWE!

CVE-2023-39910: libbitcoin_keys.txt CVE-2022-40769: profanity_keys.txt Liczba kluczy: 5 Czas: 0.1s

============================================================ BEST PRACTICES

  1. Always use both generators

    • Different vulnerabilities affect different wallets
    • Libbitcoin for BTC/LTC/DOGE/DASH/ZEC
    • Profanity specifically for ETH
  2. Generate large ranges

    • Start with 1M keys
    • Increase to 10M+ for better coverage
    • Use incremental ranges to split work
  3. Combine with other scanners

    • Feed keys to AllChainScanner
    • Check all coin types
    • Use different address formats
  4. Keep found.txt safe

    • Contains private keys
    • Never share or expose
    • Use only on addresses you own

============================================================ DISCLAIMER

⚠️ THIS TOOL GENERATES ACTUAL PRIVATE KEYS! ⚠️ ONLY TEST ON ADDRESSES YOU OWN! ⚠️ DO NOT USE FOR ILLEGAL ACTIVITIES! ⚠️ KEEP FOUND.TXT SECURE - CONTAINS PRIVATE KEYS!

The keys generated by this tool:

  • Are 64-character hex strings
  • Can control real cryptocurrency
  • Must be handled with extreme care
  • Should never be shared publicly

============================================================ RESOURCES