June 25th, 2024

Rabbit data breach: all r1 responses ever given can be downloaded

A data breach at Rabbit Inc. exposed critical API keys for ElevenLabs, Azure, Yelp, and Google Maps, compromising personal information and enabling malicious actions. Rabbit Inc. has not addressed the issue, urging users to unlink Rabbithole connections.

Read original articleLink Icon
Rabbit data breach: all r1 responses ever given can be downloaded

A data breach at Rabbit Inc. has exposed critical API keys, including those for ElevenLabs, Azure, Yelp, and Google Maps. This breach allows access to all responses ever given by R1 devices, potentially compromising personal information and enabling malicious actions like altering responses and crashing devices. Despite being aware of the issue for a month, Rabbit Inc. has not taken action to secure the API keys. The Rabbit team has been criticized for ignoring the breach and maintaining the validity of the keys. Users are advised to unlink their Rabbithole connections as a precaution. The breach highlights Rabbit's poor security practices and the risks it poses to R1 device users. Further details have not been disclosed to protect user privacy.

Link Icon 11 comments
By @chad1n - 4 months
Apparently after this was made public, they finally revoked the key which obviously broke the R1s because they didn't update the key on their server.

So this is the IT literacy of AI startups...

By @LASR - 4 months
You know what I am truly terrified of? When these AI services start keeping memories about your interactions with them to build up a full profile of you. Like chatGPT memories. But then it leaks due to a data breach.

It’s not even accurate sometimes and I definitely did not manually tell it things about me. But it made some incorrect assumptions and now it’s out there whether it’s true or not.

By @Havoc - 4 months
> rabbit team is aware of this leaking of api keys and have chosen to ignore it. the api keys continue to be valid as of writing

Remind me how many billions was this supposedly worth?

By @drodgers - 4 months
For a company who's product requires trusting them with login tokens for all your favourite online services, this is ludicrously short-sighted.
By @devonsolomon - 4 months
Move slower and break less things.
By @255kb - 4 months
This really helps with my impostor syndrome. Thanks!
By @yazzku - 4 months
It was obvious from their "key note" in day one that this project was a scam. The best thing that can happen to it at this point is for it to be sued and shut down.

Anybody can string a couple of API calls together and write an "app". That is not programming, and this project is a massive undertaking for somebody of their skill. It should have never gone to market to begin with, regulations should have stopped it on its feet. The fact that they put more effort into their "key note" than the actual product was already a red flag. It's like some marketing guys got together and decided that they were going to "take the world by storm with AI".

> we have internal confirmation that the rabbit team is aware of this leaking of api keys and have chosen to ignore it. the api keys continue to be valid as of writing.

Yeah.

By @olliej - 4 months
This provides useful context for the other story about revoking a key breaking all their services.

I wish there was a mechanism on HN to link related (but different) stories - beyond people in the comments I mean. I think it would be especially useful over time (eg I could relate these today because they’re both on front page at the same time, but if someone came across this in the future the relationship may have been lost)

By @AlwaysNewb23 - 4 months
This is why you should use a secrets manager like Doppler (https://doppler.com) or AWS Key Management Service (AWS KMS). Hardcoding your secrets or storing them in .env files will always risk something like this happening.
By @lawgimenez - 4 months
Unrelated, but what’s up with the lowercase texts?