Cowrie
cowrie.org
- Free plan
- Linux
- Self-hosted
What Cowrie is
Cowrie is a free, open-source SSH and Telnet honeypot that records brute-force attempts and activity in attackers’ shell sessions. In its default mode, it imitates a UNIX system in Python with a fake filesystem, so commands do not run on the real host. Proxy mode forwards SSH and Telnet sessions to another system while monitoring behavior. Cowrie records terminal sessions with timing information for later replay and saves files fetched with wget or curl, as well as uploads through SFTP or SCP. Its JSON logs can include logins, commands, downloads, TCP forwards, and session metadata. Output plugins connect to services and tools including Elasticsearch, Splunk, Microsoft Sentinel, MISP, VirusTotal, databases, Slack, and Prometheus. An experimental LLM backend can generate shell responses while retaining session context. Cowrie is self-hosted and can be installed through pip, Docker, or a Git checkout; local requirements include Python 3.11+ and python-virtualenv. It is BSD-licensed, began in 2014, and is maintained by volunteers.
Who it suits
Cowrie suits security researchers, CERTs, and defenders who want to observe SSH or Telnet attacks. It requires a self-hosted deployment and documented local prerequisites.
Good to know, and what to watch
- Default mode keeps attacker commands in a fake filesystem.
- Records sessions for replay with timing information.
- Captures files fetched or uploaded during sessions.
- JSON logs cover commands, downloads, and session metadata.
- Offers output plugins for security and monitoring tools.
- Cowrie is self-hosted.
- Local requirements include Python 3.11+ and python-virtualenv.
- The LLM backend is experimental.
Plans
Every plan and priceCowrie
Free plan
Getting started
- Open the Cowrie website and documentation
- Prepare a Linux host with Python 3.11+ and python-virtualenv
- Install Cowrie with pip, Docker, or a Git checkout
- Configure the emulated shell or proxy mode
- Connect output plugins to your selected logging or security services
The Club's review
Cowrie is a self-hosted SSH and Telnet honeypot for people investigating hostile connections and shell activity. It is best for security researchers, CERTs and defenders who can operate their own Linux deployment. Its standout value is the amount of session and file evidence it collects for free; it is not a managed monitoring service.
Overview
Cowrie records brute-force attempts and activity after a connection. Its default mode presents an emulated UNIX system, backed by a fake filesystem, so commands do not run on the real host. That makes it a useful decoy boundary, not a substitute for securing the machine and network that host the honeypot.
Proxy mode instead forwards SSH and Telnet sessions to another system while monitoring behavior. That can suit deployments where observing sessions reaching another host is the goal, but it does not provide the emulated shell’s separation from the real system.
Key features
Timed terminal recordings can be replayed with Cowrie’s playlog utility. Investigators can follow the sequence and pace of a session, rather than relying only on event summaries. Cowrie also saves files fetched with wget or curl and files uploaded through SFTP or SCP for later inspection.
JSON logs capture logins, commands, downloads, TCP forwards and session metadata. Output plugins connect Cowrie to a broad range of analysis and monitoring tools, including Elasticsearch, Splunk, Microsoft Sentinel, MISP, VirusTotal, Slack, Discord, databases, Graylog, Kafka, Prometheus, Datadog and Amazon S3. That flexibility is valuable when defenders already have a preferred pipeline, though configuring and operating the surrounding stack remains their responsibility.
An experimental LLM backend can generate dynamic shell responses and retain conversation context across a session. Its experimental status makes it a feature to evaluate cautiously, not a reason to depend on it for a production capture workflow.
Pricing
Cowrie is free and open source under a BSD license. The Cowrie plan costs nothing and includes the free, open-source SSH and Telnet honeypot. There is no paid tier described; the tradeoff is that deployment and ongoing operation are self-managed rather than provided as a service.
Installation is available through pip, Docker or a Git checkout. Local requirements include Python 3.11+ and python-virtualenv, so teams should be comfortable maintaining a Linux-based deployment and its dependencies.
Platforms
Cowrie is available for Linux and is self-hosted. It began in 2014 as a fork of the Kippo honeypot and is maintained by volunteers; the project credits Michel Oosterhof as creator and maintainer. Community Slack and Discord channels provide places to seek support, rather than a stated commercial support plan.
Who it's for
Cowrie is aimed at security researchers, CERTs and defenders who want to collect SSH and Telnet attack activity under their control. Its multi-layer decoy scope, credential lures, session replay, file capture and integration options make it a practical fit for investigations and monitoring workflows that can absorb the resulting data.
It is a weaker fit for organizations looking for a hosted product, turnkey support or a honeypot outside SSH and Telnet. Proxy mode also needs particular care: it forwards sessions to another system, unlike the isolated fake filesystem of the emulated shell.
Pros and cons
- Pros: Emulated shell commands stay in a fake filesystem rather than running on the real host, giving defenders a clear decoy use case.
- Pros: Timed session replay, captured transfers and detailed JSON events preserve useful investigative evidence.
- Pros: A wide selection of output plugins supports routing data into existing security, analytics and alerting tools.
- Cons: Linux self-hosting and local Python requirements put installation, maintenance and operational security on the user.
- Cons: Proxy mode forwards sessions to another system, so it does not share the emulated shell’s isolation boundary.
- Cons: The LLM backend is experimental and should not be treated as a dependable core capability.
Alternatives
For another free, self-hosted option with an API-oriented platform, consider Beelzebub, whose open-source core framework costs nothing. OpenCanary is another free, self-hosted choice if Linux and macOS support are relevant. Choose Canarytokens when free tokens deployed through its hosted service fit better than running a Linux honeypot yourself.
Honeyd is a free, GPL-licensed option for Linux, Windows and self-hosted use. MedPot is a free, self-hosted Linux alternative that requires Go 1.17 or newer. Heralding is a free, GPL-3.0 licensed open-source honeypot for Linux self-hosting. Honeytrap is another free, self-managed Linux option under Apache License 2.0. T-Pot is free and self-hosted across Linux, macOS and Windows, with hardware and network requirements to account for. Browse the Honeypot Software directory for more options.
Verdict
Choose Cowrie if you need a free, self-hosted way to study SSH and Telnet attacks with replayable sessions, captured files and flexible outputs. Its emulated shell is the clearest reason to use it, while the main reason to look elsewhere is the work of operating your own deployment—or the need for a managed service or a different honeypot scope.
The verdict
Cowrie offers two monitoring approaches: an emulated shell that keeps commands off the real host, or a proxy that forwards sessions to another system. It is free and self-hosted, with session recording, file capture, and a wide range of output plugins.
Questions people ask
How much does Cowrie cost?
Cowrie is free, with a listed plan price of free plan.
Is Cowrie open source?
Yes. Cowrie is free and open source under a BSD license.
Where can Cowrie run?
It is listed for Linux and self-hosted deployment.
What files can Cowrie capture?
It saves files fetched with wget or curl and files uploaded through SFTP or SCP.
Which integrations are available?
Output plugins include Elasticsearch, Splunk, Microsoft Sentinel, MISP, VirusTotal, Slack, Discord, MySQL, PostgreSQL, SQLite, MongoDB, Graylog, Kafka, Prometheus, Datadog, and Amazon S3.
What the maker publishes
- Deployment
- Cowrie can be installed using pip, Docker or a Git checkout, and its documentation lists Python 3.11+ and python-virtualenv as local requirements. source
- Emulated shell
- Its default shell mode emulates a UNIX system in Python with a fake filesystem and does not run attackers’ commands on the real host. source
- Founded
- 2014 source
- Integrations
- Output plugins include Elasticsearch, Splunk, Microsoft Sentinel, MISP, VirusTotal, Slack, Discord, MySQL, PostgreSQL, SQLite, MongoDB, Graylog, Kafka, Prometheus, Datadog and Amazon S3. source
- Intended users
- The project says it is used by security researchers, CERTs and defenders around the world. source
- License and history
- Cowrie is free and open source under a BSD license and began in 2014 as a fork of the Kippo honeypot. source
- LLM mode
- An experimental LLM backend can generate dynamic shell responses and maintain conversation context across a session. source
- Logging
- Cowrie logs attacker activity as JSON, including logins, commands, downloads, TCP forwards and session metadata. source
- Malware capture
- Cowrie saves files fetched with wget or curl and files uploaded with SFTP or SCP for later inspection. source
- Proxy mode
- Proxy mode forwards SSH and Telnet sessions to another system while monitoring attacker behavior. source
- Security boundary
- The feature page says the emulated shell is safe to expose because commands run in a fake filesystem and do not touch the real host. source
- Session recording
- Cowrie records terminal sessions with timing information for later replay using its playlog utility. source
- Support
- The project links users to community Slack and Discord channels. source
- What it does
- Cowrie is a medium- to high-interaction SSH and Telnet honeypot designed to log brute-force attacks and attackers’ shell activity. source
- Who maintains it
- Cowrie is maintained by volunteers, and the project credits creator and maintainer Michel Oosterhof. source
Checked against the maker's pages on 2 Oct 2026.