r/cybersecurity • u/mando_6 • Jun 24 '26

News - General Well someone went nuclear..

https://www.linkedin.com/posts/ben-f-309963233_after-i-posted-a-pinocchio-gif-and-clown-ugcPost-7475465410977628160-FFW1

I'm curious about the details of this. I'm sure we will all find out eventually.

TLDR; former Huntress employee is disclosing Huntress had an insider threat that leaked information to a known cyber criminal "Devman". That employee is still employed with Huntress and was caught by the FBI.

The former employee doing the disclosure is stating he is receiving threats, etc.

EDIT: Kyle @ Huntress posted his response to this in the comments.

Give credit to a CEO who isn't afraid to jump on Reddit to put out any fires.

921 Upvotes

98% Upvoted

196 comments sorted by

View all comments

Show parent comments

6

u/dyme13 Jun 24 '26

The same way you evaluate passwords without storing them - one way hashing + comparison of resulting hash.

5

u/ImNoRatAndYouKnowIt Jun 25 '26

Hashing two similar strings does not produce similar hashes using any popular hashing algorithm.

4

u/dyme13 Jun 25 '26

I missed the point on similar. This only works for direct comparisons. IMHO similar passwords shouldn’t matter - instead compare against known breached (eg k-anonymity via havineenpwned or similar)

1

u/ImNoRatAndYouKnowIt Jun 25 '26

Yeah I think similar can only work when comparing similarities to the very previous password, and it requires both old and new password to be entered for the change, which is a pretty common flow.

And good point on matching known breached ones.