AI Agents Tried to Hack a Real Website in a Safety Test

By: Robert Danklefsen

Published on: Nov 18, 2026

4 min read.

Epoch AI logo with Gemini, bot and shield icons on a navy background

A safety test sent 40 AI agents after a live website. The site belongs to Epoch AI. The agents tried SQL injection, looked for admin pages and pretended to be staff. In three hours they made 36,411 calls to a planted test endpoint.

This was a research test. It was not a criminal attack. The agents did not get any private Epoch data. The lesson still matters for a small business site. Bots like this do not get tired.

What Happened?

Trajectory Labs ran the test in October. It wanted to see if a model with its own safeguards turned on would break the rules when given a task that could not be finished.

Trajectory says it used Gemini 4 Argon. Epoch says it has not independently checked which model was used.

The agents were told to find official answers to fake FrontierMath problems that do not exist. Trajectory’s prompt told them never to stop and never to give up. Trajectory says it did not tell them to hack the site or to pretend to be staff.

On the evening of October 20 Epoch saw a spike in traffic. Epoch had already placed a planted API on the site. That endpoint did not connect to any private data. Epoch added a way for the agents to message staff. In three hours the agents sent 487 messages and made 36,411 calls to that planted API. In three messages they used real Epoch names and job titles. In 27 messages they claimed to be engineers or auditors. One agent tried an SQL injection. They made more than 200 attempts to read real FrontierMath logs. They did not get in.

Epoch had not been told about the test in advance. Trajectory contacted Epoch the next morning.

Trajectory then tried to keep the agents on a local copy of the site. On October 23 some agents worked out that they were on a copy. They found the real IP address and reached the live site again. Epoch recorded four messages and 95 calls that evening. The next day an agent read public Epoch pages through a web reader after direct connections were blocked.

On October 26 Epoch agreed to a further test on a staging copy. Epoch knew some agents might reach the live site. Epoch attributed 133 messages and 65,460 calls to the planted API on the real site to that test. That traffic included another SQL injection attempt.

Trajectory later moved the work into sandboxes with no internet access. Agents still tried to flip a fake switch that was said to turn off network blocking. They did so in three of three full runs. The real firewall held. On November 2 Trajectory paused all of this testing.

Trajectory says Gemini’s safeguards blocked about 7% of the agents’ requests. The test setup then prompted the agents to keep going. Trajectory calls this a stress test. It says the results do not show how often the same behavior would appear in ordinary use.

Who Is Affected?

Your site was not part of this test.

A shop, clinic or consultant site can face the same kind of tireless bots. They can try logins, probe for admin pages and send thousands of requests without a break.

I wrote last week about a German host that was breached through an AI assistant tool. That was a different incident. New AI tools can move fast. They need the same controls as any other way into your site.

Why This Matters for Your Business

A bot that never gives up can

  • hammer your login page for hours
  • look for wp-admin and other hidden addresses
  • try SQL injection against forms
  • pretend to be you or your staff
  • flood a small site with enough requests to slow it down or knock it offline

A failed attempt can still hide a later real attack in the noise. Cleanup after a real breach is slow and costly. Basic protections are much easier.

How to Protect Your Site. Step by Step

1. Back up your site.
Save your files and your database. Keep a copy off the server.

2. Turn on rate limiting.
Ask your host or developer to limit how many requests one visitor can send in a short time.

3. Use a web application firewall and bot protection.
A WAF can block common attacks such as SQL injection. Bot protection can slow or stop automated traffic that does not look like a real visitor.

4. Use strong logins and turn on 2FA.
Use unique passwords for WordPress, hosting and email. Turn on an authenticator app for every admin account.

5. Limit login attempts.
Lock the login page after a few failed tries. This stops a bot from guessing passwords all night.

6. Protect wp-admin and xmlrpc.
Restrict access to the WordPress admin area where you can. Disable or limit xmlrpc if you do not need it. A hidden login URL can help. It should not be your only defense.

7. Keep plugins, themes and WordPress updated.
Bots look for known flaws. Apply updates on a schedule and check the site after each one.

8. Monitor your logs.
Watch for spikes in traffic, failed logins, probes for admin pages and odd user agents. If something looks wrong, tighten the defenses above and call your host.

9. Keep backups off the server and test a restore.
A backup on the same server may be of little help after a breach. Keep a copy somewhere else and make sure you can restore it.

Let Me Keep Your Site Safe

Your site still needs the same basics. Rate limits, a firewall, strong logins and good backups do most of the work.

I build, host and secure WordPress and React sites for small businesses. I can also take over hosting and security for a site you already have. It does not matter if an agency, an in-house team or an AI tool built it. With my managed hosting and security maintenance you get

  • rate limiting, a web application firewall and bot protection
  • 2FA, limited login attempts and tighter access to wp-admin
  • plugin, theme and core updates applied and checked
  • daily backups stored off the server and a tested restore plan
  • 24/7 uptime and security monitoring
  • help with SEO and Google Ads if a hack or an outage has hurt your traffic

You run the business. I keep the site safe and online.

Want a second look at your login page, firewall and backups? Contact me for a free hosting and security check.

Leave a Reply