bokamba / loganvil / sshd / OpenSSH auth logs

$ loganvil generate sshd

Generate synthetic sshd / OpenSSH auth logs

Generate realistic synthetic sshd (OpenSSH) auth logs for pipeline testing, SIEM demos, and detection tuning — deterministic and 100% client-side. Each line is a real syslog-BSD auth line (timestamp, host, sshd[pid], "Failed password for … from … port … ssh2"), the exact shape your auth pipeline sees. Then inject an SSH brute-force burst — failed logins from one IP, then a success — to prove your credential-stuffing detection fires.

Open the LogAnvil generator →

This sample, generated

The block below is 15 lines of sshd / OpenSSH auth logs, produced by the real generator at seed 42 — deterministic, so this exact output regenerates anywhere. The live tool re-runs the identical engine on whatever source, seed, line count and anomalies you pick.

15lines
4.6stime span
0anomaly lines
42seed

no anomalies injected — raise a slider to seed detectable patterns

Generated sshd / OpenSSH auth logs

Real on-the-wire sshd / OpenSSH auth logs — no real users, IPs, or secrets. Copy it into a fixture, feed it to a parser, or seed a SIEM demo.

Sep 13 12:26:40 db-02 sshd[14744]: Failed password for invalid user admin from 52.94.236.248 port 37703 ssh2
Sep 13 12:26:40 app-01 sshd[20509]: Failed password for invalid user admin from 151.101.1.69 port 39823 ssh2
Sep 13 12:26:40 cache-01 sshd[10129]: Failed password for invalid user carol from 13.107.42.14 port 52152 ssh2
Sep 13 12:26:41 web-01 sshd[15479]: Failed password for invalid user www-data from 8.8.8.8 port 49490 ssh2
Sep 13 12:26:41 app-01 sshd[2118]: Failed password for invalid user carol from 34.223.14.100 port 47740 ssh2
Sep 13 12:26:41 web-02 sshd[27628]: Failed password for invalid user svc-backup from 185.199.108.153 port 41787 ssh2
Sep 13 12:26:41 web-01 sshd[1778]: Failed password for invalid user svc-deploy from 13.107.42.14 port 39689 ssh2
Sep 13 12:26:42 web-02 sshd[10018]: Failed password for invalid user postgres from 185.199.108.153 port 47109 ssh2
Sep 13 12:26:42 app-01 sshd[9671]: Failed password for invalid user alice from 52.94.236.248 port 51987 ssh2
Sep 13 12:26:42 mail-01 sshd[2973]: Failed password for invalid user root from 151.101.1.69 port 59370 ssh2
Sep 13 12:26:43 web-01 sshd[617]: Failed password for invalid user erin from 151.101.1.69 port 50043 ssh2
Sep 13 12:26:43 web-01 sshd[23607]: Failed password for invalid user root from 104.16.132.229 port 52716 ssh2
Sep 13 12:26:43 db-01 sshd[26949]: Failed password for invalid user bob from 93.184.216.34 port 48656 ssh2
Sep 13 12:26:44 app-02 sshd[18996]: Failed password for invalid user erin from 13.107.42.14 port 41885 ssh2
Sep 13 12:26:44 app-01 sshd[14792]: Failed password for invalid user www-data from 52.94.236.248 port 60830 ssh2

With an anomaly injected: SSH brute-force

The same source, regenerated with a SSH brute-force injected at 30% intensity. 6 line sare tagged and highlighted below — A burst of failed logins from one source IP, then a success — the classic credential-stuffing signature. It is a documented, detectable pattern your SIEM rules should fire on — build the test data, then prove your detection works.

Sep 13 12:26:40 db-02 sshd[14744]: Failed password for invalid user admin from 52.94.236.248 port 37703 ssh2
Sep 13 12:26:40 app-01 sshd[20509]: Failed password for invalid user admin from 151.101.1.69 port 39823 ssh2
Sep 13 12:26:40 cache-01 sshd[10129]: Failed password for invalid user carol from 13.107.42.14 port 52152 ssh2
Sep 13 12:26:41 web-01 sshd[15479]: Failed password for invalid user www-data from 8.8.8.8 port 49490 ssh2
Sep 13 12:26:41 app-01 sshd[2118]: Failed password for invalid user carol from 34.223.14.100 port 47740 ssh2
Sep 13 12:26:41 web-02 sshd[27628]: Failed password for invalid user svc-backup from 185.199.108.153 port 41787 ssh2
Sep 13 12:26:41 web-01 sshd[1778]: Failed password for invalid user svc-deploy from 13.107.42.14 port 39689 ssh2
Sep 13 12:26:42 web-02 sshd[10018]: Failed password for invalid user postgres from 185.199.108.153 port 47109 ssh2
Sep 13 12:26:42 web-02 sshd[10018]: Failed password for admin from 89.248.165.74 port 5842 ssh2SSH brute-force
Sep 13 12:26:42 web-02 sshd[10018]: Failed password for admin from 89.248.165.74 port 5842 ssh2SSH brute-force
Sep 13 12:26:42 web-02 sshd[10018]: Failed password for admin from 89.248.165.74 port 5842 ssh2SSH brute-force
Sep 13 12:26:42 web-02 sshd[10018]: Failed password for admin from 89.248.165.74 port 5842 ssh2SSH brute-force
Sep 13 12:26:42 web-02 sshd[10018]: Failed password for admin from 89.248.165.74 port 5842 ssh2SSH brute-force
Sep 13 12:26:42 web-02 sshd[10018]: Accepted password for admin from 89.248.165.74 port 5842 ssh2SSH brute-force

FAQ

Are these real sshd logs?
No — every line is synthetic. The output matches the OpenSSH syslog auth format exactly, but the usernames, hosts and IPs are fabricated. No real login attempts are involved, so it is safe for detection labs, fixtures and demos.
Can I inject an SSH brute-force?
Yes — that is the headline pattern for this source. The SSH brute-force slider appends a burst of "Failed password" lines for one user from one attacker IP, then a single "Accepted password" (the breach). Those lines are highlighted and badged so you can confirm your brute-force rule catches them.
Is the output deterministic?
Yes. Generation is fully seeded, so the same seed and config always yield byte-identical sshd lines — commit a seed to a fixture and regenerate the exact same log on any machine or in CI.

Generate other log sources

Open the LogAnvil generator to tune the seed, line count, EPS, format and anomaly sliders — or build a parser with LogForge for a log you already have.

Generate your own sshd / OpenSSH auth logs

Pick the seed, line count and EPS, inject the anomalies your rules should catch, and copy or download the result. Free, no account, nothing uploaded — generation runs entirely in your browser.

Open the LogAnvil generator →