CHYP.ai · ORBIT // Cloudy_Day Security Suite

🧪 PUBLIC DISCLOSURE · Capstone · ~9 min · 80 XP

Public Disclosure: Pinecrest Health

Check a draft disclosure against the evidence: cut overclaims, redact secrets, keep the dates honest.

SIMULATION Generated from the reviewed template [email protected] (cday-case/1), seed ikg6sj4i. Every company, person, domain and IP is fictional.

Evidence

E1: researcher notes (fictional)

Nov 11: found a public storage listing at files.pinecrest-health.example with 1,643 CSV exports named appointments_*.csv. Opened 2 files to confirm what they were (names + appointment dates). Downloaded nothing else.

E2: sample request log line (as captured)

GET /exports/appointments_0012.csv 200 auth=none key=cday_sim_d024d260426ae240 ua=curl/8.4

E3: vendor reply (fictional)

Nov 12: "Thanks, we've received your report and are investigating." Nov 31: "The listing is now private. We're reviewing access logs."

Draft disclosure: claims to check

  • The storage listing was publicly accessible without authentication.
  • About 1,643 export files were exposed.
  • Millions of patients' medical histories were stolen by criminals.
  • Pinecrest Health made the listing private 20 days after the report.
Which claim in the draft is NOT supported by the evidence?
What must you redact before publishing E2?
How many days from the report to the fix?
What does the evidence leave UNKNOWN that the write-up should say plainly?

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