Web3 developer Brian Guan lost $40,000 after accidentally making his wallet keys public on GitHub.
  • Web3 developer Brian Guan lost $40,000 after accidentally posting his wallet’s secret keys publicly on GitHub, with the funds being drained in just two minutes.
  • The crypto community’s reactions were mixed, with some offering support and others mocking Guan’s previous comments about developers using AI tools like ChatGPT for coding.
  • This incident highlights ongoing debates about security practices and the role of AI in software development within the crypto community.
  • darklamer@lemmy.dbzer0.comEnglish
    9·
    3 months ago

    The developer said he forgot that his secret keys were in the repository.

    If you have your secret keys in your repository you’ve already fucked up, long before you accidentally make that repository public.

    • BrianTheeBiscuiteer@lemmy.worldEnglish
      4·
      3 months ago

      One of the first things you should do in a repo is add a .gitignore file and make sure there are rules to ignore things like *secret* or *private* etc. Also, I pretty much never use git add . because I don’t like the laziness of it and EVERY TIME one of my coworkers checked in secrets they were using that command.

      • lurch (he/him)@sh.itjust.worksEnglish
        2·
        3 months ago

        Even though that’s a good extra precaution, per person config data, such as keys, should be stored outside of the repo, eg. in the parent directory or better in the users home dir. There is zero reason to have it in the repo. Even if you use a VM/containers, you can add the config in an extra mount/share.

      • sugar_in_your_tea@sh.itjust.worksEnglish
        1·
        3 months ago

        git add -u is pretty nice, it only adds modified files.

        I usually do git add -p which is interactive (helps avoid committing debugging prints and whatnot), but the other is nice for bigger refactors.

      • JimmyMcGill@lemmy.worldEnglish
        1·
        3 months ago

        I basically always do a git add -p

        Very useful command and it works with other git commands as well.

        Everytime a colleague asks me for help with git that’s the one rule I suggest them to use.

          • PumaStoleMyBluff@lemmy.worldEnglish
            2·
            3 months ago

            Instead of just adding whole changed files, it starts an interactive mode where it shows every hunk of diffs one by one, and asks you to input yes or no for each change. Very helpful for doing your own mini code review or sanity check before you even commit.

  • k_rol@lemmy.caEnglish
    6·
    3 months ago

    I’m sad I didn’t see any comments saying he shouldn’t be using a $40k wallet key to test his software in the first place. Anything could happen with simple code mistakes…just get an empty wallet or one with a few bucks in it.

  • Johanno@feddit.deEnglish
    41·
    3 months ago

    They made 2 errors.

    1. Use crypto

    2. Storing the key anywhere close to the repo.

  • dhork@lemmy.worldEnglish
    2·
    3 months ago

    I have no sympathy for him, if he is a crypto developer he knows how important those private keys are. And he also knows people scrape public areas all the time looking for keys just like that. The whole point of crypto is to be immutable, so that money is simply lost to him now.

    He seems to know how much of a dumb mistake that was, although his description of himself was a bit more colorful.

    • CallMeButtLove@lemmy.worldEnglish
      1·
      3 months ago

      You’re not wrong about how important those keys are and how he definitely should have known better. But I at least have a little sympathy for the guy. Everyone makes mistakes from time to time, even with important stuff. Hopefully they are lucky enough not to lose 40k on one but unfortunately he wasn’t. Whether he should have known better or not, that just plain sucks.

    • redcalcium@lemmy.instituteEnglish
      1·
      3 months ago

      The whole point of crypto is to be immutable, so that money is simply lost to him now.

      IIRC there are several cases where some group of people lost big enough coins and force most of the miners to fork to get their money back. Not bitcoin though.

  • lowleveldata@programming.devEnglish
    1·
    3 months ago

    It must be automated for it to happen in 2 minutes. Which implies these kind of things happen often enough for someone to write a script for it.

    • tiramichu@lemm.eeEnglish
      1·
      3 months ago

      Yes, it absolutely is automated.

      There are bots running constantly looking for things that match patterns for exploitable credentials in public commits.

      AWS credentials

      SSH keys

      Crypto wallets

      Bank card info

      If you push secrets to a public github repo, they will be exploited almost immediately.

      • daddy32@lemmy.worldEnglish
        0·
        3 months ago

        The scanning part is definitely automated by many different actors (for the gains or the “lulz”), but being this fast, also automated key usage (account draining) must have been implemented which is a bit more impressive…

        • Voroxpete@sh.itjust.worksEnglish
          1·
          3 months ago

          Not really. All of the underlying mechanics of crypto are so simple that they can be very easily interacted with by bots. Bots make up the vast majority of all crypto trades; mostly wash trading, but also front-running attacks, scams or outright thefts like this one. There are so many exploitable flaws in crypto that every bug is basically a self-executing bug bounty.

    • partial_accumen@lemmy.worldEnglish
      1·
      3 months ago

      If it was a script I wrote, it would have successfully stolen the $40k, but also stolen my own money and deposit both sets of money into a second intended victims account because I forgot to clear a variable before the main loop runs again.

  • 👍Maximum Derek👍@discuss.tchncs.deEnglish
    0·
    3 months ago

    If there was any sort of password / highly entropic string detection in their build pipeline it would have caught a wallet’s keys. They aren’t an excuse for lack of diligence, but they should still be in every pipeline where passwords or keys might have to get used.

    I’m terrible about building pipelines for most of my personal projects though, so I’m throwing rocks from my glass house here.

    • sugar_in_your_tea@sh.itjust.worksEnglish
      2·
      3 months ago

      A CI pipeline wouldn’t fix this since the code would be committed before the pipelines run. This needs to be caught on the dev’s machine with a pre-commit or pre-push hook.

    • barsquid@lemmy.worldEnglish
      1·
      3 months ago

      I like your CI plan but maybe they just needed some sort of sane policy. Like never commit plaintext keys to any repo. Never work with a $40k key in a new project under development. Never convert a private repo to public.

  • Jo Miran@lemmy.mlEnglish
    0·
    3 months ago

    I use a text file version of a novel to back up my keys, then I store the key map in multiple cloud drives. For example, if the word is “lighting” then my key map for that word would be 487,5 (line 487, word 5). Easy to crack, if you know what novel I am using.