this post was submitted on 17 Dec 2025
327 points (98.5% liked)

Lemmy Shitpost

36103 readers
3724 users here now

Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.

Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means:

-No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...

If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.


Also check out:

Partnered Communities:

1.Memes

2.Lemmy Review

3.Mildly Infuriating

4.Lemmy Be Wholesome

5.No Stupid Questions

6.You Should Know

7.Comedy Heaven

8.Credible Defense

9.Ten Forward

10.LinuxMemes (Linux themed memes)


Reach out to

All communities included on the sidebar are to be made in compliance with the instance rules. Striker

founded 2 years ago
MODERATORS
 

https://pleroma.envs.net/objects/522868a1-ef60-45e4-9ac3-0d37967907b8

Alt: google warning about one compromised password due to a data breach, saying "This account is at risk: pringles.com"

the image is captioned: "IF YOU HAVE A PRINGLES.COM ACCOUNT CHANGE IT IMMEDIATELY"

you are viewing a single comment's thread
view the rest of the comments
[–] sylver_dragon@lemmy.world 11 points 1 day ago (2 children)

I deal with this sort of thing pretty regularly for the company I work for. We get threat intelligence from several vendors when they see our users show up in "dumps". Basically, threat actors will package up stolen credentials in a large zip file and make that available (usually via bittorrent) for anyone to download. Security vendors (e.g. Mandiant, which Google bought) download those dumps and search for accounts associated with their customers and send out these warnings when they find one. On the customer side, if the breach was recent we'll force a password reset and warn the user about the breached password, with a recommendation to change their password on the affected site and also change any passwords which might be similar elsewhere.

Why do we force the password reset, even when it wasn't the account for our business which was breached?
There's a couple reasons for this. First off, people still reuse passwords all the fucking time. Maybe this victim didn't, but we have no good way validate that. Second, even without direct reuse, folks like to have one main password that they apply slight variations to. They might use "Hunter 42!" at one site and then "Hunter 69*" at another. This isn't smart, attackers know you do this and they have scripts to check for this. Lastly, if an organization is following the latest NIST guidance, you're not changing your password on a regular cadence anymore. With that is the expectation that passwords will be rotated when there is a reason to suspect the credentials are compromised. Ya it's annoying, but that's part of the trade-off for not having to rotate passwords every six months, we pull the trigger faster on forced rotations now.

If you get one of these, consider it a good time to think about how you come up with and store passwords. If you are re-using passwords, please turn off your computer/device and don't come back to the internet until you have thought about what you have done. If you aren't already using one, please consider a password vault (BitWarden or KeePassXC make great, free choices). These will both help you create strong passwords and also alleviate the need to memorize them. Just create a strong master passphrase for the vault, let it generate the rest of your passwords as unique, long (12+ character) random junk, and stop trying to memorize them (with the exception of your primary email account, that gets a memorized passphrase).

[–] bandwidthcrisis@lemmy.world 5 points 1 day ago (1 children)

if an organization is following the latest NIST guidance, you're not changing your password on a regular cadence anymore.

Lol.

[–] sylver_dragon@lemmy.world 2 points 1 day ago

Sadly, yes a lot of organizations didn't get the memo. But this really is the current guidance. In NIST 800-63B Section 5.1.1.2:

Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.

[–] Demdaru@lemmy.world 2 points 1 day ago

unverified_schmuck unv3r1f1ed-schmuck UnvERIfied^sChMuCk

The hell you mean passowrds the same.