This is unreasonably sensationalized.
You’d be better served to read Wiz’ post instead: https://www.wiz.io/blog/wiz-research-uncovers-exposed-deepse...
DeepSeek responded well to Wiz’ responsible disclosure by closing the database access. DeepSeek have yet to disclose results, if any exist, of forensic analysis. Even though the door was accidentally left wide open, there may be no actual breach.
If DeepSeek has another issue of the exact same type, you’ll know they’re not learning about production. But this has so far been a once-off. For now it’s fair to assume a mistake was made once and they quickly rectified it when made aware, which is as good as you can hope for from a relatively fledging operation.
