
Honeypot
A honeypot is a computer system deliberately made to look vulnerable in order to lure attackers. It serves no real purpose other than one: to observe and record anyone who touches it.
A honeypot is a computer or service that exists purely as bait. It looks like a worthwhile target: a poorly secured database, a forgotten server, an account with the password “admin123”. In reality, there’s no real data stored there. No one at the company has any reason to use this system. That’s exactly the trick: any access is automatically suspicious. The name comes from the honey pot that lures bears — except here, instead of honey, the pot contains fake prey.
What bait reveals that an alarm can’t
Normal security systems have a fundamental problem: they must distinguish real traffic from false traffic. A large corporate network sees millions of accesses every day. The vast majority are harmless. As a result, a warning system constantly raises false alarms, and eventually nobody pays attention anymore. Experts call this alert fatigue, and it’s one of the most common causes of missed intrusions.
A honeypot flips this problem on its head. Because no legitimate traffic occurs there, there are practically no false alarms. Whoever logs in has either made a typo by accident or has something illicit in mind. A single hit is therefore a strong signal, not noise.
On top of that comes the intelligence gained. Defenders watch which tools an attacker uses, which commands they type, and where they intend to send stolen data. Security firms operate entire networks of honeypots to collect new malware before it hits real victims.
From an open login to a replicated network
Technically, the range spans from very simple to very elaborate. A simple honeypot merely pretends a service exists. It accepts a connection, logs the username and password, and then drops the connection. This is cheap and low-risk, but it will only fool an attentive attacker for a few seconds.
More elaborate variants are complete operating systems in an isolated environment. There, the attacker can genuinely move around, create files, and launch programs. Everything gets recorded. Such systems must be strictly separated from the real network. Otherwise the bait becomes a gateway, and the defender has built themselves a vulnerability.
A leaner variant uses individual lure data instead of entire systems: a document named “Salaries 2025” that triggers an alert as soon as it’s opened. Or credentials that aren’t valid anywhere — whoever tries them has stolen them. These are called honeytokens. Incidentally, a common misconception is that a honeypot wards off attacks. It doesn’t. It detects and documents them; other systems have to do the defending.
From bank servers to traps for AI crawlers
In businesses, honeypots are a standard tool for larger security departments, such as at banks or cloud providers. You also encounter the principle in everyday life, usually without noticing. Many web forms contain an invisible input field. Humans don’t see it and leave it blank. Automated bots fill in everything and thereby give themselves away. That’s how sites filter out spam without making you solve an image puzzle.
Recently, the term has also come up in the dispute over AI training data. Website operators create pages that only automated scraping programs can find. Whoever fetches them has ignored the site’s rules. Some such traps fill themselves with endlessly generated nonsense to keep the scraper busy and spoil its results.
In the news, you’ll also often come across the term in connection with cryptocurrencies. There, a honeypot refers to a manipulated contract where you can deposit money but never withdraw it again. That’s simply fraud and shares nothing with the security technique except the idea of bait. So it’s worth paying brief attention to the context when reading.