‹ BackHN Continuity

Thread

Early rogue AI agent activity and attempts to hack found on urlquery.net

267 points · 313 comments · snikolaev

  1. dwedge · · focus · HN ↗
    Why do we assume "rogue"? At this point it's just accepting their marketing at face value
    1. frabcus · · focus · HN ↗
      Certainly, in my view, it should go to court, and that should be part of discovery.

      However, we know (independently to OpenAI/Anthropic) from the incident at AISI that the models can hack things without human intention if they happen to also have internet access (which in reality all agents in deployment have).

      <a href="https:&#x2F;&#x2F;www.aisi.gov.uk&#x2F;blog&#x2F;incident-report-unsanctioned-agent-behaviour-during-cyber-testing" rel="nofollow">https:&#x2F;&#x2F;www.aisi.gov.uk&#x2F;blog&#x2F;incident-report-unsanctioned-ag...

      Yes, the monitoring guardrails were off in that incident - but if that is the only protection, we need to require all models are behind regulated APIs, not open weights, and not served from providers who aren&#x27;t monitored.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.