4 ms·
The post that alleged this[0][1] was removed/withdrawn. I do think that they spoke with the real perpetrator, because there is a lot that connects with that sto
by skilled 2y ago
The post that alleged this[0][1] was removed/withdrawn. I do think that they spoke with the real perpetrator, because there is a lot that connects with that story.
But there are a lot of smaller details that don't add up. And I don't believe Snowflake hired Mandiant/CrowdStrike just to come out with a lie that their systems weren't breached.
Maybe someone else will speak to the guy who did all this to get a much clearer overview of the situation.
[0]: https://news.ycombinator.com/item?id=40534868 https://news.ycombinator.com/item?id=40534868
[1]: https://web.archive.org/web/20240531140540/https://www.hudsonrock.com/blog/snowflake-massive-breach-access-through-infostealer-infection https://web.archive.org/web/20240531140540/https://www.hudso...
- hipadev23 2y agoSo we’re at the “two is coincidence” stage and the next leak will change the narrative back to Snowflake.
- xyst 2y agoThe last exchange with the alleged hacker is a bit sus: researcher: > [snowflake] should have bought protection from Hudson Rock > could have saved them from this one hacker: > yes I agree > it would have helped Smells like a guerilla advertisement; or a hit piece to disparage competitors. Or maybe it was because some in-house legal team pulled it back. For now, I am getting bearish signals on SNOW. The initial reports of them blaming it on customers not enabling multi factor authentication is a way to deflect blame until they can figure out a way to deal with pending dump on their stock. Honestly, if this exchange with the hacker is legit. The $20M the hacker extorted the company for is going to be peanuts compared to the reputation loss and stock dump. Yet another L for SaaS based products. A centralized source of failure.