What we've done and what's next:
• Patched the vulnerable endpoint and restored the monitor-layer sender binding
• Removed all 774 fake notifications from user inboxes
• Restored Beeper after patching and verification
• Auditing every remaining API route for missing authentication or similar gaps
• Adding regression tests for auth on all identity-bearing endpoints
• Keeping heightened monitoring in place as service resumes
To everyone who saw the fake notification, and to the team for the disruption this caused — we're sorry. This should not have been possible, and the responsibility sits with us.
Thank you to the people who flagged it early, to for digging into the onchain history, and to for the public warning that helped limit the damage.
If you have concerns about your account or received the fake notification, DM directly.
https://farcaster.xyz/cassie/0x5e0c9eba
The post this replies to
The post this quotes
Terminus needs JavaScript to show replies and pictures.