Scraping Pastebin for private keys

A pastebin is a text storage site and the largest one is Pastebin.com itself. Pastebins have many legit uses, such as sharing code with others (the original intended use), but over the years, pastebins have also become go-to places for dodgy affairs such as doxing.

Every now and then, people unintentionally share stuff not meant for the public domain. Such as Bitcoin private keys. Uh-oh.

Therefore, pastebins are regularly scraped using various programs and scripts (and bots), of which EMAGNET is a prime example.

We decided to test how fast we will be robbed. For this purpose, we have sent 0.0001 BTC to

3PastegzjwWvK6Ao34NMPZU9XDZ8yq1gsE

with this transaction id.

… and – this is the key part – published its private key as a public paste without an expiry date. We will not link to the exact paste here (yet); we won’t do all the work for you.

We’ll give you humans and bots a couple of hours. We hypothesize that someone will indeed sweep the 10k satoshi, but we have been wrong before and we will not be super-surprised if we’re able to transfer it back tomorrow.

It will be exciting to see how fast pastbin scrapers are with Bitcoin. Whatever happens, we will of course link to the paste, after someone else took the coins, or when we took them back.

Good hunting! Comments or questions?

One more thing!

Consider the donation address at the bottom of the page. We re-invest all contributions into new projects for btcleak.com. Help us create new content and remain ad-free forever. Thank you.

7 Replies to “Scraping Pastebin for private keys”

  1. After two full hours, no one has claimed the coins. Strange! Here is the paste

    https://pastebin.com/dBP5Y9wE

    We will give you a couple of minutes more.

    Reply

  2. Pastebin wasn’t as nasty as we thought it would be. The private key was exposed for almost 3 full hours until we swept it back, in mint condition (well, minus transaction fees)

    https://www.blockchain.com/btc/tx/eab1e0d2a435e9f68b15935114fb16cd0e957f6c5c69a166d65c15f3012dbb97

    Reply

  3. Now that the transaction is finally confirmed – it was in the mempool for 6 long days due to its very low transaction fee – we can furthermore conclude no one took the opportunity to steal it “in transit”, as the private key was disclosed here AND “replace by fee” (RBF) enabled, meaning you could have rerouted our transaction back to your own address with a higher transaction fee. Too late now 🙂

    Reply

  4. Just Curious to know July 28, 2020 at 6:57 AM

    How to create vanity p2wpkh-p2sh address??

    Reply

    1. Just Curious to know July 28, 2020 at 7:02 AM

      These 2 keys results in different address, KzjG6Ufq4ENPPEjvGFRgPLsvhmcgxhewYV5L4iLetn4zNaNmP4bA, 68B6C3B3F287C9F7E7AEBEB01689033788B6F930580CA2ADB6CCC6DA63F2B225 for 1F2CyMWjhnu5Jq22yG1nq2Qfx17wRMou5K, 1LS5pDx7jhYXWhVmnXxakMqpbD31RMa2c. Then how can we get a vanity address 3PastegzjwWvK6Ao34NMPZU9XDZ8yq1gsE with the same private key??

      Reply

  5. Hi there! Every 32-byte hexadecimal private key corresponds to (at least) FOUR different Bitcoin public addresses, explained here:

    https://btcleak.com/2020/06/13/import-all-private-keys-in-electrum-the-right-way/

    We used this tool to create the vanity address

    https://github.com/JeanLucPons/VanitySearch
    https://github.com/JeanLucPons/VanitySearch/releases

    Simply “vanitysearch -gpu -stop -t 0 -3Paste”

    We good?

    Reply

    1. Just Curious to know July 29, 2020 at 9:03 AM

      You are the best…
      Lots of Love 🙂

      Reply

Leave a Reply

Your email address will not be published.