If you run a website, a shop, or even a shared inbox, AI security just became part of your job description — whether you signed up for it or not. A fresh round of research flips the usual advice on its head: instead of building a taller wall to stop attacking AI agents, you build a maze, fill it with fake doors, and let them burn their own time and money finding out none of it's real. In controlled AWS tests, that approach made attacking agents take up to 8× longer and spend 23× more per objective. Stack all nine techniques together and four different models finished with a big, fat zero.
What happened
The research was shared on Reddit by user /u/tracebit and focuses on deception — deliberately feeding attackers misleading information so they chase ghosts instead of your real data. The tests ran in a controlled AWS environment, which just means a sandbox on Amazon's cloud rather than a live customer system. Nobody's actual business was on the line.
The numbers are the whole story. Attack agents took up to 8× longer to get anywhere, and every objective cost 23× more. Then the team combined all nine techniques into one setup and ran 40 attempts. Kimi, Qwen, DeepSeek and GPT-5.6 Cyber all reached zero objectives. Not fewer. Zero.
A quick translation of the jargon
An AI agent is a program that's been handed a goal and the freedom to take steps toward it on its own — think of a contractor who shows up with a clipboard and a set of keys instead of waiting for you to point at the bathroom. An "objective" is whatever it was told to grab: a password, a file, admin access. Deception means the environment lies to it. Fake admin pages, decoy logins, files that look valuable and aren't.
That's it. No magic. The point isn't to trap the attacker forever. It's to make every step cost them something, so the math stops working in their favor.
What it means for you
You don't need a security team for this to matter. Attacks are getting automated, which means defense has to be cheaper than the attack. Wasting an attacker's time and money is the entire game — and you can play it at almost any scale. If you want to see how cheap automation has gotten, the free AI tools at MyKreaTool will show you in about ten minutes, no signup gymnastics required.
At home
Your router, your smart plugs, that NAS drive full of photos. An attacking agent doesn't care whether it's hitting a bank or a bedroom — it cares whether the door opens easily. A decoy device name, an empty "admin" folder, and a guest Wi-Fi network that leads nowhere are the household version of a fake safe in the hallway. It won't make you bulletproof. It makes you the boring target that isn't worth the electricity bill.
At work
Most offices now have AI assistants reading email and poking around shared drives. If an agent goes wandering in that space, it heads straight for the obvious names: passwords.docx, payroll, final_final_v3. Renaming sensitive files and planting obvious-but-empty decoys buys your IT people the one thing they never have enough of — time to notice.
For a small business
This is where the 23× figure really lands. Attacker economics are a spreadsheet. If a successful hit costs pennies, they'll hit everybody. If every attempt costs 23 times more and takes 8 times longer, you quietly fall off the list. A decoy checkout page and a fake customer database can do more for a small shop than another security plugin nobody logs into.
For students and teachers
Schools are swimming in AI agents now — grading helpers, chatbots, plagiarism checkers. Deception has a gentler use here: honeypot assignments that flag themselves the moment they're submitted, decoy answer files that don't exist. It's the difference between chasing every cheat and making cheating take so long that nobody bothers.
For creators and anyone earning online
If your income runs through a store, a newsletter, or a course platform, your real risk is downtime and account takeover. Decoy admin URLs and fake "backup" folders are cheap and take an afternoon. And keeping your actual money-makers behind a second layer — two-factor on the payment dashboard — still beats any clever trick.
How to try it right now
You don't need a research lab. Start free, then scale up if it works for you.
1. Free option first. Fire up the free AI tools at MyKreaTool and use them to draft your decoys: a fake "employee handbook" page, a dummy admin portal, a few throwaway CSV files with realistic headers and garbage rows. Ten minutes of prompting gets you filler that looks plausible.
2. Borrow a free attacker. Pick an open model named in the study — DeepSeek or Kimi — and give it a simple goal against a test page you own. Watch where it goes and what it clicks first.
3. Install the cheapest trick. Rename your real admin login and put a decoy at the obvious URL. Nothing behind it but a form that logs every attempt.
4. Time both runs. Note how long the model takes to reach the real page with and without the decoy. That gap is your personal 8×.
5. Count requests per success. If a real goal used to take three tries and now takes sixty, you've got your 23× in miniature.
6. Keep the boring basics. Updates, backups, two-factor. Deception is a layer, not a replacement.
Upsides and what changes
The appeal here is that deception attacks the attacker's budget instead of your own. You're not outspending anyone — you're adding friction that costs you almost nothing to maintain and costs them real money per step. For a solo founder or a two-person shop, that's a much better deal than buying another subscription tool and hoping someone reads the alerts.
It also changes what "good defense" looks like. A decade of advice said harden everything, patch everything, close every port. That still matters, but the research suggests diminishing returns compared to making the target confusing. An agent that hits eight dead ends in a row starts looking like a bad investment — and bad investments get abandoned, not escalated.
What shifts in practice
You'll start budgeting in time and tokens rather than in licences. You'll care more about what an attacker sees than about how thick the wall is. And you'll probably write down your decoy inventory, because plants that look too real can create their own mess — which brings us to the honest part.
Limitations
A controlled AWS sandbox is not the open internet, and forty runs across four models is a solid result, not a law of nature. The setup combined all nine techniques at once — that's a lot of configuration for a normal person to build without breaking something, and the study doesn't hand you a ready-made product to install. Models improve fast, so tricks that stalled Kimi, Qwen, DeepSeek and GPT-5.6 Cyber today may look obvious to whatever ships next year. Decoys can also backfire: fake records that resemble real customer data can tangle you up in privacy rules, and a decoy page that's too convincing might confuse your own staff or your own monitoring. This is one layer. It doesn't replace patching, backups or two-factor, and it won't stop a determined human who's already inside.
Conclusion
The takeaway is refreshingly simple: you don't have to outgun an attacking AI agent, you just have to make it waste time and money until it gives up. An 8× slowdown and a 23× cost bump are enough to turn a cheap attack into an expensive one — and four models scoring zero across 40 runs shows just how far that goes when the tricks stack up.
Your one action today: open MyKreaTool, generate three decoy files with believable names, and drop them where an agent would look first. Twenty minutes, zero cost, and your first real step toward being the target nobody bothers with.
Comments 0