News for hackers. Stuff that matters.
Re:Exposed DeepSeek database leaking sensitive information, ... by nico on Wednesday January 29, 2025 @05:52PM (#42872345)
So much effort in trying to tarnish DeepSeek the last 24hrs
Re:Exposed DeepSeek database leaking sensitive information, ... by sho_hn on Wednesday January 29, 2025 @06:00PM (#42872435)
Can't fault hackers for taking a look at a website that goes from "virtually unknown" to "extremely popular and headline news globally" practically over night. If nothing else, the probability of low-hanging fruit in something that is barely battle-tested is high.

You can fault them for disclosure practices though :-)

Re:Exposed DeepSeek database leaking sensitive information, ... by htrp on Wednesday January 29, 2025 @06:41PM (#42872862)
> Wiz Research has identified a publicly accessible ClickHouse database belonging to DeepSeek, which allows full control over database operations, including the ability to access internal data. The exposure includes over a million lines of log streams containing chat history, secret keys, backend details, and other highly sensitive information.

>The Wiz Research team immediately and responsibly disclosed the issue to DeepSeek, which promptly secured the exposure.

It seems like Wiz told deepseek and deepseek secured this vuln?

Re:Exposed DeepSeek database leaking sensitive information, ... by khazhoux on Wednesday January 29, 2025 @06:05PM (#42872480)
Are you saying this report was falsified, or that the press should keep things like this secret?
Re:Exposed DeepSeek database leaking sensitive information, ... by LarsKrimi on Wednesday January 29, 2025 @08:13PM (#42873622)
Probably they are rather suggesting that there are a lot of unscrupulous western companies with a lot to lose who might have an interest in convincing certain people to skip responsible disclosure
Re:Exposed DeepSeek database leaking sensitive information, ... by khazhoux on Wednesday January 29, 2025 @09:26PM (#42874102)
The vulnerability was fixed before the disclosure, so that's a non-issue here.
Re:Exposed DeepSeek database leaking sensitive information, ... by rnd0 on Thursday January 30, 2025 @05:22AM (#42876520)
It would be very nice if the press didn't just fall over itself trying to be a free PR agency for OpenAI.
Re:Exposed DeepSeek database leaking sensitive information, ... by krick on Wednesday January 29, 2025 @06:10PM (#42872537)
Maybe, but having dev services outside of VPN is pretty nuts, not much effort needed to find that. Wouldn't expect a company with such budgets be that careless, I'm sure it's only the tip of the iceberg.
Re:Exposed DeepSeek database leaking sensitive information, ... by meiraleal on Wednesday January 29, 2025 @06:42PM (#42872866)
One more proof that AGI is not near
Re:Exposed DeepSeek database leaking sensitive information, ... by gruez on Wednesday January 29, 2025 @06:02PM (#42872458)
I'm not sure why you think why this discovery has to be some sort of "effort in trying to tarnish DeepSeek". Deepseek is the #1 downloaded app and and the media can't stop talking about it. That means a lot more people are looking into the app and possibly finding vulnerabilities, no conspiracy needed.
Re:Exposed DeepSeek database leaking sensitive information, ... by talldayo on Wednesday January 29, 2025 @06:16PM (#42872606)
Not to mention the same thing happened to OpenAI and basically the same effort went into shaming them: https://www.theverge.com/2024/7/3/24191636/openai-chatgpt-ma...
Re:Exposed DeepSeek database leaking sensitive information, ... by skupig on Wednesday January 29, 2025 @06:08PM (#42872517)
edit: snip, misinfo, I'm illiterate. Sorry!
Re:Exposed DeepSeek database leaking sensitive information, ... by ZeWaka on Wednesday January 29, 2025 @06:37PM (#42872822)
> instead of following responsible disclosure practices

They literally did, though? They were resolved before publishing.

Re:Exposed DeepSeek database leaking sensitive information, ... by skywhopper on Wednesday January 29, 2025 @06:23PM (#42872692)
What are you talking about? They did follow responsible disclosure.
Re:Exposed DeepSeek database leaking sensitive information, ... by immibis on Wednesday January 29, 2025 @06:38PM (#42872828)
No idea why this is downvoted.

Responsible disclosure normally means you wait up to 90 days so they can fix it, before you disclose it to the public. In this case, it was fixed immediately, so they disclosed it to the public immediately.

Which is another thing it seems Chinese corporations do better than American ones.

Re:Exposed DeepSeek database leaking sensitive information, ... by xmprt on Wednesday January 29, 2025 @06:01PM (#42872441)
I, for one, think this is a valuable piece of information and somewhat interesting analysis. You can take the cynical point of view that this was released just to tarnish their reputation or you can assume that it's security researchers publishing an important discovery just like they've always done whether it's for OpenAI, Microsoft Copilot, or any other AI or non AI product.
Re:Exposed DeepSeek database leaking sensitive information, ... by nyclounge on Wednesday January 29, 2025 @06:12PM (#42872554)
>https://news.ycombinator.com/item?id=42871371#42872454

We all agree this kind of leak should be disclosed. However normally security researchers don't just leaks specific URL and etc. This may be what the parent is referring to.

Re:Exposed DeepSeek database leaking sensitive information, ... by kdmtctl on Wednesday January 29, 2025 @08:20PM (#42873676)
I think that was a shameless self promotion. A lot of PR and free traffic by taking a low hanging fruit. Nothing else. But they did some good though.
Re:Exposed DeepSeek database leaking sensitive information, ... by zhengiszen on Wednesday January 29, 2025 @06:05PM (#42872484)
you're absolute right, so much garbage propaganda in many languages. For Apple we have tv news that usually promotes new Apple or OpenAI products (wtf!!) that are trying to tarnish DeepSeek on the privacy level... No words about all those garbage software siphoning off the web (without respecting neither copyright nor privacy)
[dead]
Re:Exposed DeepSeek database leaking sensitive information, ... by kranner on Wednesday January 29, 2025 @07:33PM (#42873318)
I don't know about 1-4 and 5 seems an honest mistake.

Is there a source for the misleading GPU count? Dario cites Dylan Patel, and pt 4 cites Alexander Wang, but these are just claims so far.

As far as censorship regarding Chinese history, does it matter? The other models have other areas that are censored. Is anyone planning to use LLMs to look up historical facts anyway?

Stealing IP? That's rich coming from AI companies that mined the entire public internet. Did they get permissions from copyright holders in every instance?

And if DeepSeek did evade particular US sanctions whose only justification seems to be to prop up US's economic hegemony over the rest of the world (unlike sanctions against weapons, invasions and human rights violations), then good for them.

Re:Exposed DeepSeek database leaking sensitive information, ... by lysace on Wednesday January 29, 2025 @06:52PM (#42872957)
It would be incredibly immature and naive to presume that the data fed to this service is not going to be data mined by the CCP.

Downvoted - because of course the CCP wouldn't want all of this data, that's preposterous. What would they even do with it? /S

Re:Exposed DeepSeek database leaking sensitive information, ... by mandmandam on Wednesday January 29, 2025 @05:56PM (#42872385)
Yep.

Kinda like how your comment was grey within 1 minute, despite stating an objective truth.

Sure, this is to be expected given the billions and billions of dollars at stake but like - that money is gone lol. DeepSeek isn't going back in the bottle, nor is open source AI in general.

Re:Exposed DeepSeek database leaking sensitive information, ... by IncreasePosts on Wednesday January 29, 2025 @06:07PM (#42872504)
The comment isn't wrong, but the implication is at deep seek is somehow special and is getting undue attention from hackers. Any app that skyrockets from nowhere to number one in the app store overnight will have the attention of probably hundreds of thousands of hackers.
Re:Exposed DeepSeek database leaking sensitive information, ... by mandmandam on Wednesday January 29, 2025 @07:01PM (#42873045)
> the implication is at deep seek is somehow special and is getting undue attention from hackers

... It is special.

There was over a trillion dollars wiped from tech stocks lol, in a massive win for consumers and the planet. You can't say this is like Flappy Bird or something.

Re:Exposed DeepSeek database leaking sensitive information, ... by IncreasePosts on Wednesday January 29, 2025 @07:13PM (#42873163)
The stock market does all sorts of silly things. If the stocks recover in 2 weeks to where they were, will that be deep seek erasing $1T and tech re-earning $1T? Or deep seek doing nothing?
Re:Exposed DeepSeek database leaking sensitive information, ... by codr7 on Wednesday January 29, 2025 @07:27PM (#42873270)
The damage was done, if it was 100% based on truth or how fast they recover has nothing to do with it.
Re:Exposed DeepSeek database leaking sensitive information, ... by mandmandam on Wednesday January 29, 2025 @07:31PM (#42873305)
> The stock market does all sorts of silly things.

For sure. This one was pretty clear though. It's exactly what you'd expect when a moat evaporates overnight.

Even if tech stocks recover in 2 weeks (doubt) an open source model comparable to o1 with a 50x efficiency gain is still not just another app. Which means there will be bad actors with a special interest in spreading narratives on every relevant forum...

Re:Exposed DeepSeek database leaking sensitive information, ... by rnd0 on Thursday January 30, 2025 @05:21AM (#42876514)
>Which means there will be bad actors with a special interest in spreading narratives on every relevant forum

Which brings us neatly to OpenAI

Re:Exposed DeepSeek database leaking sensitive information, ... by breakitmakeit on Wednesday January 29, 2025 @09:01PM (#42873915)
Elsewhere perhaps, this seems like a pretty standard/legit security flaw in a new application which is found and hopefully quickly closed.

If your information is sensitive, do not use an LLM by public API - absolutely all of your data is being stored and processed. For all of them.