Files
deadface-challenges/database/after-the-lock/README.md
T
2026-10-19 14:59:45 +02:00

32 lines
2.0 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# After the Lock
**Category:** Database
**Points:** 150
## Description
\<iframe src="" style="background-image: url('https://deadface.sfo3.cdn.digitaloceanspaces.com/2026/img/wayfinder/after_the_lock.png');background-size:cover;background-position:center center;background-origin:content-box;background-repeat:no-repeat;background-color:rgba(40, 40, 40,0);min-height:80px;height:130px;width:100%;padding:10px;border:none" title="Thumbnail">\</iframe>
\<sup>Created By: \<code>@syyntax\</code>\</sup>
\<style>
.tiny-text {
font-size: 6px;
color: #1a1a1a;
}
\</style>
\<span class="tiny-text">flag{4f4ed17cd1090c92}\</span>
​‌‌​​‌‌​​‌‌​‌‌​​​‌‌​​​​‌​‌‌​​‌‌‌​‌‌‌‌​‌‌​‌‌‌​​‌‌​​‌‌​​​​​‌‌​‌‌​​​‌‌‌​‌‌​​​‌‌​​‌‌​‌​‌‌‌‌‌​‌‌​‌‌​‌​​‌‌​​‌‌​‌​‌‌‌‌‌​‌‌​‌​​​​​‌‌​‌​​​‌‌‌​​‌​​‌‌​​‌​​​​‌‌​​‌‌​‌‌‌​​‌​​‌​‌‌‌‌‌​‌​​​​​‌​‌​​‌​​‌​‌​‌‌‌‌‌​‌‌​​‌​​​​‌‌​‌​​​‌‌​​‌​​​‌‌​​‌​​​‌‌‌‌​​‌​‌‌‌‌‌​‌
Once a clinical trial's database is locked, results are frozen — any edit after the data-lock date is a protocol violation and a fingerprint of tampering. Aurora Health recorded the official lock date for the Veltrexa study right in the studies table. Find the subject whose primary efficacy result (measure = 'primary_efficacy_delta') was modified after the study's data-lock date, and report their subject code.
Use the provided MySQL shell.
Submit the subject code as `deadface{subject_code}`. Example: `deadface{ABCD-0101}`.
[Access Database](https://aurora.dctf.io)
## Services
- [https://deadface.sfo3.cdn.digitaloceanspaces.com](https://deadface.sfo3.cdn.digitaloceanspaces.com)
- [https://aurora.dctf.io)](https://aurora.dctf.io))