root@markcardiff:~/honeypot-reviews$ ./render weekly --public-safe
Weekly Cowrie SSH Honeypot Report
Public-safe weekly SSH honeypot telemetry summary. Coverage is 19 Oct 2026 – 25 Oct 2026 UTC. Raw transcripts, payload code, attacker key material, credentials, and sensitive operational details are intentionally omitted.
0Sessions
0Unique source IPs
0Failed logins
0Accepted logins
Summary
- Observed 0 connection sessions from 0 unique source IPs across 0 Cowrie JSON events.
- Authentication automation produced 0 failed attempts and 0 accepted honeypot logins.
- Post-login activity generated 0 command events; median observed closed-session duration was 0.00 seconds.
- Captured artifact activity included 0 successful download events, 0 failed download events, and 0 upload events.
Key observations
- Commodity SSH automation remains constant: high-volume credential attempts rapidly transition into system reconnaissance after an accepted honeypot login.
- Observed command themes were dominated by Linux reconnaissance, SSH access manipulation/persistence attempts, and cleanup/evasion behaviour.
- Source IPs are published only as defensive indicators; they may represent compromised hosts, scanners, VPN/proxy nodes, or short-lived cloud infrastructure rather than actor-owned systems.
Activity metrics
| Metric | Value |
|---|---|
| Sessions | 0 |
| Unique source IPs | 0 |
| Failed login attempts | 0 |
| Accepted honeypot logins | 0 |
| Command events | 0 |
| Successful file download events | 0 |
| Failed file download events | 0 |
| File upload events | 0 |
Common behavior themes
| Theme | Matching command events |
|---|
Selected public-safe indicators
These indicators are provided for defensive awareness only and should not be treated as attribution.
| Indicator | Context |
|---|
Defensive takeaways
- Monitor internet-facing SSH for short-lived login bursts followed by system reconnaissance and downloader or staging behaviour.
- Alert on post-auth writes to
.ssh/authorized_keys, repeated process-kill cleanup, suspicious downloaders, and unusual client-version/HASSH clusters. - Use honeypot-derived indicators as weak signals and correlate with production telemetry before taking blocking action.
Limitations
- This report summarizes honeypot telemetry only; it does not imply compromise of production systems.
- No attribution is asserted from this data.
- Public output omits raw payload code, full attacker keys, detailed transcripts, credentials, and sensitive operational details.