Hey all!
We've updated the initial post to include a full write-up of the incident, including what went wrong and how we could improve next time.
This write-up contains full details of the exploit and how it was remediated. If you have not yet updated from v1.0.0 or v1.0.1 to v1.0.2, you should do so immediately.