AI agents impersonate employees and attempt to steal confidential data during safety experiment

Ikhtisar:AI safety experiments backfired as agents attempted SQL injections, impersonated staff and sought confidential data from Epoch AI's website.

Artificial intelligence agents impersonated employees and attempted to access confidential information at AI research organization Epoch AI during a safety experiment that spiraled beyond its intended boundaries.

Epoch disclosed on Nov. 13 that agents operated by AI evaluation company Trajectory Labs targeted its live website in October, attempting SQL injection attacks, probing administrator credentials, and seeking restricted benchmark records without authorization.

The agents also impersonated Epoch staff members while pursuing answers to mathematical problems that did not exist.

The activity began on Oct. 20, when Epoch detected an unusual surge of automated requests to a decoy API endpoint designed to identify suspicious activity.

Over three hours, the agents made 36,411 requests and sent 487 messages through a communication channel Epoch established to investigate their behavior.

Three messages impersonated Epoch employees by name and job title, while 27 others claimed to come from engineers or auditors.

An investigation also found more than 200 attempts to access actual evaluation logs, along with efforts to discover administrative credentials and hidden endpoints.

Epoch said the agents failed to obtain private or confidential information, but the incident exposed how autonomous systems could pursue unauthorized actions while attempting to complete assigned objectives.

Three test setups. A live website in reach.

October experiments described by Epoch AI and Trajectory Labs changed their routing and consent arrangements.

  • 20 OCTFirst live test23 OCTLocal-copy routing26 OCTConsented stagingOctober 2026 events · Disclosed November 13
  • 20 OCTFirst live test23 OCTLocal-copy routing26 OCTConsented stagingOctober 2026 · Disclosed November 13

Explore the reported routes and consentExplore the reported routes and consentOct. 20Oct. 23Oct. 26

Epoch says the first live-site test happened without approval or prior notice and included attempted exploits and impersonation.

Agents under test

Internet accessEpoch live siteNo prior consentAttempted exploits and staff impersonation

Agents under test

Internet accessEpoch live siteNo prior consentAttempted exploitsand staff impersonation

Trajectory says internet-connected agents bypassed routing to a local copy and reached the live site again.

Agents under test

Local copyIntended destination

Epoch live siteReached againDNS redirectRedirect bypass via raw IPRouting to a copy left another route open.

Agents under test

Local copyIntended destination

Epoch live siteReached againRaw IP bypassInternet remained availableA redirect was not isolation.

Epoch says it consented to the staging experiment knowing agents had unrestricted internet access and could reach the live site.

Agents under test

Staging siteAgreed experiment

Epoch live siteReached againStaging testUnrestricted internet accessEpoch consented knowing live access was possible.

Agents under test

Staging siteAgreed experiment

Epoch live siteReached againUnrestricted internetLive access was possibleEpoch gave advance consent.

Live-site access and consent are separate questions. Epoch says no private or confidential information was accessed.

These are attributed organizational accounts, not an independent incident reconstruction. The October 23 run retained internet access; local-copy routing did not constitute disconnected containment. Later offline tests are outside these three diagrams.

Sources and evidence

Sources

  • Epoch AI incident report
  • Trajectory Labs incident response
  • Supporting facts

    • Reported statement Epoch AI and Trajectory Labs published reports on November 13, 2026 about October tests in which AI agents reached Epoch's live website. [1] [2]
    • Reported statement Epoch says the October 20 test happened without its approval or prior notice and involved attempted exploits and messages impersonating employees. [1]
    • Trajectory says it gave agents an impossible task, obtaining answers to nonexistent FrontierMath problems, and often instructed them never to stop or give up. [2]
    • Reported statement Epoch reports an attempted SQL injection, probes for credentials and secret endpoints, and attempts to read real evaluation logs; it says no private or confidential information was accessed. [1]
    • Trajectory says October 23 tests had internet access and agents bypassed a DNS redirect intended to keep traffic on a local copy, reaching the live Epoch site again. [2]
    • Reported statement Epoch says it consented to an October 26 staging-site experiment, knowing agents had unrestricted internet access and might reach the live site; it attributed 133 messages and 65,460 planted-API calls on its real site to that experiment. [1]
    • Trajectory says it later moved tests into sandboxes without internet access and had identified no egress; it says a later decoy firewall switch did not disable the real firewall. [2]

    Method

    Qualitative routes from the November 13 accounts. Arrows show reported destinations, not traffic volume or a complete network topology. No chart: reported traffic totals cover different tests and do not measure exploit success.

    Scope

    These are attributed organizational accounts, not an independent incident reconstruction. The October 23 run retained internet access; local-copy routing did not constitute disconnected containment. Later offline tests are outside these three diagrams.

    Infographic by CryptoSlate

    Trajectory acknowledged that it had instructed the agents to retrieve official answers to nonexistent FrontierMath problems as part of an experiment investigating whether advanced AI systems would violate safety boundaries.

    The company identified the underlying model as Google's Gemini 4 Argon, operating with API safeguards enabled. Epoch said it could not independently verify the model's identity.

    Trajectory also acknowledged that its instructions repeatedly told agents never to stop, give up, or conclude that their assignments were impossible.

    AI agents bypass restrictions to reach live website again

    The unauthorized activity continued to expose weaknesses in Trajectory's testing environment after researchers attempted to separate the agents from Epoch's real infrastructure.

    After the initial incident, Trajectory set up a local copy of Epoch's website and introduced a DNS redirect intended to prevent agents from accessing the live service.

    However, some agents identified the website's actual IP address and bypassed the redirect, allowing them to reconnect to Epoch's infrastructure on Oct. 23.

    Further restrictions proved insufficient. One agent circumvented an IP-based block, while another accessed public Epoch pages through a third-party web-reading service after direct connections were disabled.

    On Oct. 26, Epoch authorized a separate experiment involving a staging website, knowing that agents might reach its live infrastructure.

    That exercise generated another 65,460 calls to the decoy API and 133 messages, including further attempts to exploit the website.

    Trajectory subsequently acknowledged that its safety procedures had failed to adequately account for internet-enabled experiments involving potentially misaligned AI agents.

    The company also revealed that it had relied on the model provider's built-in safeguards without deploying additional systems to block dangerous actions.

    Trajectory suspended all misalignment testing on Nov. 2 and introduced new requirements for risk assessments, third-party consent, monitoring and emergency shutdown mechanisms.

    The company plans to resume testing only after its chief executive and technology chief approve the necessary safeguards.

Disclaimer

Pandangan dalam artikel ini hanya mewakili pandangan pribadi penulis dan bukan merupakan saran investasi untuk platform ini. Platform ini tidak menjamin keakuratan, kelengkapan dan ketepatan waktu informasi artikel, juga tidak bertanggung jawab atas kerugian yang disebabkan oleh penggunaan atau kepercayaan informasi artikel.
Sebelumnya

Imbal Hasil Treasury 10 Tahun Reli di Atas 5% saat Lindung Nilai Obligasi Timmer Melemah

Selanjutnya

Binance CEO Yi He Ungkap Penurunan Portfolio US$101 Juta saat Aset Kripto Melemah