News for hackers. Stuff that matters.
Re:Reverse engineering Lyft Bikes for fun (and profit?) by ibigio on Thursday January 22, 2026 @12:03PM (#46721929)
Howdy.

Back in 2019 I reverse engineered the lyft bikes api to unlock them from my bed. It's one of my favorite stories, and after telling it dozens of times I finally decided to write it up in its full technical glory.

I used to love learning about security through blog posts/writeups, so I tried to include as much detail as possible. Let me know if you like this style!

Re:Reverse engineering Lyft Bikes for fun (and profit?) by spydum on Thursday January 22, 2026 @03:32PM (#46724765)
Believe it or not, straight to jail! Just kidding, great writeup. I know it's not groundbreaking, but does surprise me how many products don't bother with rate limiting controls.
Re:Reverse engineering Lyft Bikes for fun (and profit?) by ibigio on Thursday January 22, 2026 @05:51PM (#46726152)
i actually think a quick-fix was setting a rate limit. which sadly thwarted my brute-forcing, but did not actually fix the race condition itself. though it's a very fair "kid, stop it" response until they fixed the race condition.
Re:Reverse engineering Lyft Bikes for fun (and profit?) by storystarling on Friday January 23, 2026 @02:34PM (#46736775)
Rate limiting is a stopgap, not a fix. I would have expected a transaction lock in Postgres (SELECT FOR UPDATE) to serialize the requests. Or a Redis mutex if they are worried about database contention.