А для тех кто прокси не доделал?
Spam bots cracked the honeypot in our Joomla form builder extension.
We were proud of it. It had worked for years.
Then suddenly, a flood of betting links and garbage.
Time to rethink everything.
For years, we relied on a classic honeypot to stop spam:
• A fake input type="text"
• Hidden with CSS (display:none, positioned off-screen)
• Randomized field name/id like cf-field-xyz123
• Inserted server-side with PHP, part of the DOM
• Designed to trick bots into filling it out
It worked… until it didn’t.
Bots evolved.
They ignore display:none, detect name patterns, scan for “trap” fields.
Eventually, spam shot up. It was time to fight back.
I was convinced bots could now run JavaScript.
So I rebuilt the honeypot from scratch — this time, fully JS-based.
• It is injected via JavaScript after the form is ready
• It uses a random, unique name/id per session
• It’s hidden with inline CSS (display:none) targeting its unique ID.
• The field is added to the payload
On the server side, the logic is simple:
If the honeypot field is missing or not empty, it’s flagged as spam.
Now here’s the interesting part:
I expected bots to fill the honeypot. Instead, every flagged submission had the field missing entirely from POST data.
🤯 That means bots couldn’t run the JS that generates the field.
Is this a headless browser limitation? A shortcut to skip JS after page load?
No idea. But it works.
Spam dropped.
No CAPTCHAs. No friction.
Just one invisible field they keep missing.
If you’ve got theories, I’m all ears.