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

https://rabbitu.de/articles/security-disclosure-1

by dcchambers • 2 years ago

192 33 2 years ago

yazzku• 2 years ago

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.

llamaimperative3• 2 years ago

I mean that is definitely programming. The real distinction you’re looking for is the gap between programming and building a production-ready product.

RIMR• 2 years ago

I see no benefit in being pedantic. Obviously writing code that performs simple API interactions is "programming". The definition of programming is extremely broad.

It is rather clear to me that yazzku is saying that the programming required to pull of what the R1 does falls well below what Rabbit promised their customers. That this is such a bullshit design that we can infer that the entire product is a scam, because if they were serious it wouldn't be so obvious that no work into actually making a useful product.

hughesjj• 2 years ago

Imo it's programming, but not engineering.

sandwitches2• 2 years ago

I have bad news about most SaaS products.

VTimofeenko• 2 years ago

If claims from this[1] video by Coffezilla are to be believed, the r1 is not their first questionable project.

https://www.youtube.com/watch?v=NPOHf20slZg

Retr0id2• 2 years ago

The r1 is not just not-their-first, it's a pivot that reuses code from their earlier endeavours. (which itself is fine, like, that's what you'd expect from a pivot, it's just that their PR strategy relies on claiming those past projects are wholly unrelated.)

When they rug-pulled GAMA (after selling a bunch of NFTs), as consolation prize they "open sourced"[0] a few things.

One of their many promises was that their space-station "metaverse" would have "Quantum Engine AI Integration" (letting you talk to NPCs, among other things). They released a lightly edited Unreal Engine game template (the "metaverse"), along side a file named `api.yml`[1] which documents an AsyncAPI[2] API (the "AI integration"). There is no actual integration, the API spec is just positioned adjacent to the Unreal project - there's a note in the README that amounts to "integrate it yourself".

The back-end component was never open-sourced, and they've long since shut down the API server, but based on the docs, the API used by the r1 is clearly a direct evolution of that design.

As for the R1's API, there is no documentation, but I partially reverse-engineered it and wrote some docs of my own[3], which is enough to see the similarities.

[0] https://github.com/gamaspacestation/

[1] https://github.com/gamaspacestation/gss_release/blob/main/ap...

[2] https://www.asyncapi.com/

[3] https://gist.github.com/DavidBuchanan314/aafce6ba7fc49b19206...

officeplant• 2 years ago

I swear all these shitty startups need is that clean look from Teenage Engineering to sell worthless garbage.

devonsolomon• 2 years ago

Move slower and break less things.

AdamJacobMuller• 2 years ago

"move fast and break things" is an excuse for how this could have happened (not that i'm defending it) but the last bits of the article...

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

That's just damning. Making the mistake is one thing, but, having it pointed out to you and refusing to fix it is unconscionable.

Havoc• 2 years ago

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?

Hamuko• 2 years ago

Reportedly only some hundreds of millions. The makers of that stupid AI Pin that you strap onto your chest and that catches on fire was trying to sell itself to Hewlett-Packard for $1 billion.

drodgers• 2 years ago

For a company who's product requires trusting them with login tokens for all your favourite online services, this is ludicrously short-sighted.

al_borland• 2 years ago

I have very little trust in startups. Even if the R1 was a good product, their methods of logging into services was something I could never get onboard with.

I even changed banks (after 20 years), because I was looking to link my account to a budget app and my old bank required a 3rd party service that cached login data. I went through and tried connecting about 2 dozen banks that seemed like contenders to find the 2 or 3 that allowed me to authenticate properly with a token I could revoke from the bank itself, and switched to one of those. I don't know who these people are that hand over things like bank creds based on trust alone. The R1 wasn't there yet, but I'm cure that was a future goal.

chad1n• 2 years ago

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...

kotaKat• 2 years ago

As jesse himself said on the Rabbit Discord:

"please don't under estimate the effort and IQ level of our eng - its much more complicated than that."

I present no other commentary.

oth001• 2 years ago

"Trust me bro"

rsynnott2• 2 years ago

Bigly IQ leveled. The best.

olliej• 2 years ago

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)

Retr0id2• 2 years ago

https://news.ycombinator.com/item?id=40793192

LASR• 2 years ago

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.

askonomm• 2 years ago

Pretty sure they already do that, at least in some way, with OpenAI thinking about or already doing ad injecting via giving priority to certain types of services or products.[0]. All in all the company has so far been quite dishonest so I have no reason to think otherwise.

[0] https://www.adweek.com/media/openai-preferred-publisher-prog...

lawgimenez• 2 years ago

Unrelated, but what’s up with the lowercase texts?

JCharante• 2 years ago

It was the trend earlier this year amongst terminally online tech twitter users.

rsynnott2• 2 years ago

It comes and goes; it was also big in the late 90s.

255kb• 2 years ago

This really helps with my impostor syndrome. Thanks!

AlwaysNewb23• 2 years ago

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.

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

Related Stories