CHYP.ai · ORBIT // Cloudy_Day Security Suite

🧪 CLOUD IDENTITY · 5-minute starter · ~4 min · 30 XP

Cloud Identity: Impossible travel?

Read a sign-in log from a fictional identity provider and spot the account-takeover pattern.

SIMULATION Generated from the reviewed template identity@1.0.0 (cday-case/1), seed d20261121. Every company, person, domain and IP is fictional.

Evidence

HaloID sign-in log (fictional identity provider, fictional tenant)

TimeUserAppResultCityIP
08:15 UTCivan.petrov@harbor-cdn.exampleMailsuccessNairobi192.0.2.28
08:19 UTCeli.novak@harbor-cdn.exampleMailsuccessLisbon192.0.2.36
08:22 UTChana.sato@harbor-cdn.exampleMailsuccessToronto192.0.2.4
08:24 UTCana.ruiz@harbor-cdn.exampleMailsuccessNairobi192.0.2.226
08:27 UTCana.ruiz@harbor-cdn.exampleMailsuccessNairobi192.0.2.226
08:33 UTCjo.mensah@harbor-cdn.exampleMailsuccessWarsaw192.0.2.227
08:37 UTCjo.mensah@harbor-cdn.exampleMailsuccessOsaka203.0.113.14
08:41 UTCana.ruiz@harbor-cdn.exampleWikisuccessNairobi192.0.2.226
08:46 UTCdara.kim@harbor-cdn.exampleWikisuccessDenver192.0.2.87
Which attack pattern does the log show?
Which account should you treat as compromised first?
Which source IP should go in your incident notes?

Playing as a guest: you'll see your score and the reasoning, but nothing is saved. Join (one click, no email) to earn XP.

Want a different one? New variant ↻

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