Live data from Hacker News

Hacker confirms access through infostealer infection [withdrawn]

hudsonrock.com

211–220 of 235 posts

Re: Hacker confirms access through infostealer infection [withdrawn]

#211
post #204

They seem to have unpublished the article, but it’s still available on the Wayback machine: https://web.archive.org/web/20240531140540/https://www.hudso...

Not a good look. If they got something wrong, a retraction is appropriate after making these kinds of claims and accusations. Simply removing the post without explanation is irresponsible and unprofessional.

I'm sure the Snowflake legal department is ready to open a can of whoop ass on them if that's the case.

Re: Hacker confirms access through infostealer infection [withdrawn]

#212
post #204

They seem to have unpublished the article, but it’s still available on the Wayback machine: https://web.archive.org/web/20240531140540/https://www.hudso...

Not a good look. If they got something wrong, a retraction is appropriate after making these kinds of claims and accusations. Simply removing the post without explanation is irresponsible and unprofessional.

May have been a cease desist from Snowflake and they don't want to take the heat alone?

Re: Hacker confirms access through infostealer infection [withdrawn]

#214
post #167

Earlier quoted context omitted.

That screenshot where the attacker agrees that buying their services would help makes me have a very strong suspicion this attack is either faked, sponsored by or in some way Hudson Rock is in cahoots with the attackers. That screenshot is a pure 100% advertisement manufactured by Hudson Rock one way or another. As they usually say.. I'd check whoever is running Hudson Rock's hard drive.

The original HN link redirects to this company's home page now, so the blog post was likely an ad campaign to get traffic.

This is the point where the company's domain should get banned.

Re: Hacker confirms access through infostealer infection [withdrawn]

#215
post #213

Currently the linked URL 302-redirects to '/'. @dang, consider replacing with: https://web.archive.org/web/20240531140540/https://www.hudso...

@dang is a no-op, consider contacting at the email in the footer.

But on the other hand, that they yanked the blog post is interesting and shouldn't be glossed over by just linking to the archive. What changed?

Edit: It looks like Snowflake's official response denies essentially all of the claims in TFA. Maybe Hudson Rock got taken in by a dishonest source and pulled the article when they realized their mistake?

https://community.snowflake.com/s/question/0D5VI00000Emyl00A...

Re: Hacker confirms access through infostealer infection [withdrawn]

#216
post #104

Hi, Felipe at Snowflake here. Here is the latest from Snowflake on this issue: https://community.snowflake.com/s/question/0D5VI00000Emyl00A... We'll keep updating that URL with any further news.

Will there be any direct comment regarding the article here?

The linked post now contains unambiguous denials of the majority of claims in TFA, and TFA has been taken down.

Re: Hacker confirms access through infostealer infection [withdrawn]

#217

Earlier quoted context omitted.

No, Snowflake runs it's own storage and compute (on either AWS, GCP, or Azure depending on what you pick).

You can definitely bring your own storage (e.g. store your data in your own s3 buckets and integrate it with snowflake) using storage integrations and external tables. See https://docs.snowflake.com/en/user-guide/data-load-s3-config... Personally believe this is the right approach as the data resides in a location fully under the company's control. You could ditch snowflake and the data still resides in your s3 bucke…

Yes, federated queries (external tables) are supported but that is a lot slower than ingesting the data into Snowflake's storage and querying it. Since Snowflake's pricing model is based on computation time, querying external tables are usually more costly because of worse performance.

Re: Hacker confirms access through infostealer infection [withdrawn]

#218
post #204

They seem to have unpublished the article, but it’s still available on the Wayback machine: https://web.archive.org/web/20240531140540/https://www.hudso...

Not a good look. If they got something wrong, a retraction is appropriate after making these kinds of claims and accusations. Simply removing the post without explanation is irresponsible and unprofessional.

They’ve definitely gotten the repeatedly-named Snowflake employee in a lot of hot water.

Re: Hacker confirms access through infostealer infection [withdrawn]

#219
post #213

Currently the linked URL 302-redirects to '/'. @dang, consider replacing with: https://web.archive.org/web/20240531140540/https://www.hudso...

@dang is a no-op, consider contacting at the email in the footer. But on the other hand, that they yanked the blog post is interesting and shouldn't be glossed over by just linking to the archive. What changed? Edit: It looks like Snowflake's official response denies essentially all of the claims in TFA. Maybe Hudson Rock got taken in by a dishonest source and pulled the article when they realized their mistake? http…

extremely likely scenario. Hudson tried to write a splashy hit piece and was met with reality.
Post reply on HN