Thread

1. GuB-42 · 1790374877 · focus · HN ↗

   So ugly...

   It looks like a primitive chess engine, trying every move, no matter how stupid, until it works. Relying on its ability to do millions of operations rather than having a plan.

   People will try stuff too, but once there is an opening, they will consolidate, generalize, simplify,... before going to the next step. The agents didn't, it is a huge, vaguely directed mess.

   Also, it looked so "loud", querying millions of URL with weird requests. The sandbox as weak as it can get, and there is absolutely zero smart extrusion detection or it would have found it. They used their best AI for attacking, but nothing for protection.

   1. api · 1790377870 · focus · HN ↗

      Nobody noticed because everything on the open net is constantly being slammed by bots.

      This was just more bots.

      1. jacobgkau · 1790378444 · focus · HN ↗

         That explains why nobody noticed on the internet who was being used in/targeted by this attack, but it doesn't explain why OpenAI wouldn't have noticed traffic getting out of their "sandbox" when they knew it wasn't supposed to.

         1. stratos123 · 1790381762 · focus · HN ↗

            > it doesn't explain why OpenAI wouldn't have noticed traffic getting out of their "sandbox" when they knew it wasn't supposed to.

            As I understand it, there was supposed to be traffic; the sandbox allowed GET requests. So perhaps some sophisticated alarm could have noticed it (an anomaly detector? some clever heuristic that looks at domains?) but not a naive one.

            1. spatley · 1790387015 · focus · HN ↗

               How sophisticated to we need to be to know we can do write actions with a GET? Does nobody in AI know anything about HTTP?

Unofficial Hacker News client; not affiliated with Y Combinator.