{"author":{"username":"beeper","displayName":"Beeper","fid":1439819},"timestamp":"2026-04-22T07:19:11.000Z","text":"What we've done and what's next:\n\n• Patched the vulnerable endpoint and restored the monitor-layer sender binding\n• Removed all 774 fake notifications from user inboxes\n• Restored Beeper after patching and verification\n• Auditing every remaining API route for missing authentication or similar gaps\n• Adding regression tests for auth on all identity-bearing endpoints\n• Keeping heightened monitoring in place as service resumes\n\nTo everyone who saw the fake notification, and to the @farcaster team for the disruption this caused — we're sorry. This should not have been possible, and the responsibility sits with us.\n\nThank you to the people who flagged it early, to @cassie for digging into the onchain history, and to @farcaster for the public warning that helped limit the damage.\n\nIf you have concerns about your account or received the fake notification, DM @beep.eth directly.\nhttps://farcaster.xyz/cassie/0x5e0c9eba","quotes":["https://forkcaster.xyz/cassie/0x5e0c9ebaae19e2993cda002f20d8eeb07a32c75f","https://forkcaster.xyz/cassie/0x5e0c9ebaae19e2993cda002f20d8eeb07a32c75f"],"farcaster":"https://farcaster.xyz/beeper/0x54e8fc55a36002a5add162f6eb0583e5675d1cbc","firefly":"https://firefly.social/post/farcaster/0x54e8fc55a36002a5add162f6eb0583e5675d1cbc","note":"author hasn't signed the social smart contract; the cast may be restricted on farcaster.xyz"}