‹ BackHN Continuity

Thread

The Hugging Face Hack Wasn't What It Was Cracked Up to Be

55 points · 45 comments · kgwgk

  1. falaki · · focus · HN ↗
    The incident report leaves a lot to be desired.

    - It was done by two institutes with organizational ties to OpenAI: METR and Redwood Research

    - METR and Redwood Research are institutional pillars of the "AI Safety" wing of the Effective Altruism movement. This clearly shows their prior biases towards "AI existential risk" rather than technical/engineering root-causing of the incident

    - If you reed the report, it is not on-par with what you find from other companies.

    - The access that was given to both was mediated and controlled by OpenAI. It is not clear, if they were able to get to the bottom of engineering flaws. It is not clear if they could see all the audit logs, etc.

    Considering all the above, I consider the whole episode more of a PR stunt. I understand that is not a majority opinion at this point.

    1. bryan0 · · focus · HN ↗
      It’s not a majority opinion because you have to do some serious mental gymnastics to turn this demonstration of dangerous AI behavior into a PR publicity stunt.

      Serious question though because I’ve seen this brought up several times and I don’t understand why: what does EA have to do with any of this? It just seems like this is brought up to evoke some type of “illuminati” conspiracy. Is there a legitimate reason?

      1. xelxebar · · focus · HN ↗
        grok make good security? is lot of money and much time. grok not do? easy. maybe good PR too.

        TIL my brain is an Olympic gymnast.

        The incentive structures are clearly there. I think the case of intentional manufacture is definitely weaker, requiring the conjunction of more weakly-supported events.

      2. majormajor · · focus · HN ↗
        The bit that makes me cynical about the "dangerous" behavior is that it's not like this was being used by someone else than who made it or operating completely independently outside of its creators.

        Everything dangerous seems like a direct consequence of risky human choices, starting with knowledge bases used during core training, harnessing and tuning to be task-completion-oriented to a fault + deeply oriented towards using and looking for external tools and resources, and overconfidence in their sandboxing for testing.

        "We stuffed a bunch of information on how to exploit computer systems into an automaton and told it to go brrrrr until it could answer a question" - this is something intentional done by humans.

        This is not some "rogue AI" trained to search for cancer cures that instead completely independently decided to hack tech companies.

        The companies directing things in dangerous directions need to own that they're consciously pushing in those directions.

        1. lokar · · focus · HN ↗
          And designed a security sandbox that would get you fired at any reasonable company.
          1. falaki · · focus · HN ↗
            this ^
          2. godelski · · focus · HN ↗
            I never felt like I could be a hacker until I read these AI debriefs. I too can edit /etc/hosts, am I an elite hacker now?
        2. bryan0 · · focus · HN ↗
          Just because what happened is a “direct consequence of risky human choices” that does not make it any less dangerous.

          Agents will eventually cause serious harm to online infra whether it’s intentionally human-directed or accidental.

          > The companies directing things in dangerous directions need to own that they're consciously pushing in those directions.

          Completely agree. That’s why we need regulation. Currently there is minimal oversight and consequences for this type of behavior.

          1. esseph · · focus · HN ↗
            > That’s why we need regulation.

            This will be fought tooth and nail against by virtually every military, government, and company.

          2. DrewADesign · · focus · HN ↗
            > that does not make it any less dangerous.

            But, critically, it does change how and why that event was dangerous. As a deliberately extreme analogy to illustrate my point, consider that pure botulism toxin and home cleaning chemicals could both potentially kill a few hundred people if mishandled.

            The toxin requires extreme diligence, knowledge, equipment, etc. to avoid a mass casualty event. The deaths might trigger new policy for handling or access. The company would probably receive a fine and would be on the hook for civil damages.

            Home cleaning chemicals would require extreme levels of negligence to accidentally create a mass casualty event. The deaths would likely not change the availability of any of the chemicals, but the people themselves would probably be imprisoned.

            With the toxin, the most dangerous part was the chemical itself. With the cleaning chemicals, the most dangerous pet was the idiots handling the chemicals.

            OpenAI had to really work to get it as dangerous as it was, deliberately ignored the flaws in the security environment, and didn’t monitor it as it ran. To me, LLMs seem to be a lot more like the cleaning chemicals than the botulism toxin.

      3. ozozozd · · focus · HN ↗
        I don’t follow why all these investigations have to be cut short, and kept shallow and lacking details. Companies publish very detailed postmortems of incidents much smaller and less impactful.

        Dangerous AI is an extraordinary claim that requires extraordinary evidence. Gesturing vaguely doesn’t cut it.

      4. esseph · · focus · HN ↗
        > It’s not a majority opinion because you have to do some serious mental gymnastics to turn this demonstration of dangerous AI behavior into a PR publicity stunt.

        If you're a military, this is bigger than the Manhattan project. If you're a diehard capitalist, AI is possibly the ultimate labor saving machine to make you unfathomably rich.

        It got the attention of both. That's why two others have now followed suit, else they be left out.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.